On Fri, Jul 10, 2009 at 11:22 PM, danben <dan...@gmail.com> wrote:

>
> What I have seen, however, is that the number of open FDs steadily
> increases
> with the number of cores opened and files indexed, until I hit whatever
> upper bound happens to be set (currently 100k).  Raising machine-imposed
> limits, using the compound file format, etc are only holdovers.  I was
> thinking it would be nice if I could keep some kind of MRU cache of cores
> such that Solr only keeps open resources for the cores in the cache, but
> I'm
> not sure if this is allowed.  I saw that SolrCore has a close() function,
> but if my understanding is correct, that isn't exposed to the client.
>
> Would anyone know if there are any ways to de/reallocate resources for
> different cores at runtime?
>

We are currently working on a similar use-case. What we've done is that
we've added a lazy startup option to a core with a LRU based core
loading/unloading. We did this through modifying CoreContainer and extending
CoreAdminHandler. This feature is marked for 1.5. We plan to give a patch as
soon as the code for 1.4 is branched off. Some related changes are already
in trunk e.g. SOLR-943, SOLR-1121, SOLR-921, SOLR-1108, SOLR-920.

The pending issues are:
https://issues.apache.org/jira/browse/SOLR-919
https://issues.apache.org/jira/browse/SOLR-1028
https://issues.apache.org/jira/browse/SOLR-880

-- 
Regards,
Shalin Shekhar Mangar.

Reply via email to