lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson (JIRA)" <>
Subject [jira] [Commented] (SOLR-1293) Support for large no:of cores and faster loading/unloading of cores
Date Tue, 23 Oct 2012 15:47:13 GMT


Erick Erickson commented on SOLR-1293:


I'm not sure I understand this. As I'm looking at this particular implementation, all the
potential cores (configuration, data files, etc) are already on the particular node, it's
just a matter of loading/unloading them. If you're thinking about SolrCloud/ZK, oh my aching
head! I guess I'd propose that how this all works with ZK be split off to different tickets
all together, too much for me to deal with....

I'm explicitly thinking of this as having no cluster-awareness, it's all local to a single
Solr node. Any meta-level coordination on which node a particular query _should_ be routed
to is assumed to be out of scope, at least for this version.

That said, I can certainly see the value in what you're talking about, that's just not the
use-case I'm trying to address....
> Support for large no:of cores and faster loading/unloading of cores
> -------------------------------------------------------------------
>                 Key: SOLR-1293
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: multicore
>            Reporter: Noble Paul
>             Fix For: 4.1
>         Attachments: SOLR-1293.patch
> Solr , currently ,is not very suitable for a large no:of homogeneous cores where you
require fast/frequent loading/unloading of cores . usually a core is required to be loaded
just to fire a search query or to just index one document
> The requirements of such a system are.
> * Very efficient loading of cores . Solr cannot afford to read and parse and create Schema,
SolrConfig Objects for each core each time the core has to be loaded ( SOLR-919 , SOLR-920)
> * START STOP core . Currently it is only possible to unload a core (SOLR-880)
> * Automatic loading of cores . If a core is present and it is not loaded and a request
comes for that load it automatically before serving up a request
> * As there are a large no:of cores , all the cores cannot be kept loaded always. There
has to be an upper limit beyond which we need to unload a few cores (probably the least recently
used ones)
> * Automatic allotment of dataDir for cores. If the no:of cores is too high al the cores'
dataDirs cannot live in the same dir. There is an upper limit on the no:of dirs you can create
in a unix dir w/o affecting performance

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message