lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <>
Subject [jira] [Commented] (SOLR-1028) Automatic core loading unloading for multicore
Date Wed, 31 Oct 2012 00:56:13 GMT


Mark Miller commented on SOLR-1028:

bq. As you said, though, I suspect we'll be hashing this all out in the "how to bring this
all together" discussion, wherever we have it.

I guess my point is that we should hash things out first. If you are going in a non solrcloud
compatible direction with all of these massive core issues, I think that is a mistake. You
are adding a bunch of code and complication that will just make it harder to pull away from
the old style solr and into a cleaner new world. You may be creating features we will have
to continue supporting or rip away from users shortly after they are added. Both things may
not be a good idea.

Developing along the old Solr model and just hoping everything will converge in the end seems
like the wrong approach.
> Automatic core loading unloading for multicore
> ----------------------------------------------
>                 Key: SOLR-1028
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: multicore
>    Affects Versions: 4.0, 5.0
>            Reporter: Noble Paul
>            Assignee: Erick Erickson
>             Fix For: 4.1, 5.0
>         Attachments: SOLR-1028.patch, SOLR-1028.patch
> usecase: I have many small cores (say one per user) on a single Solr box . All the cores
are not be always needed . But when I need it I should be able to directly issue a search
request and the core must be STARTED automatically and the request must be served.
> This also requires that I must have an upper limit on the no:of cores that should be
loaded at any given point in time. If the limit is crossed the CoreContainer must unload a
core (preferably the least recently used core)  
> There must be a choice of specifying some cores as fixed. These cores must never be unloaded

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