lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-1028) Automatic core loading unloading for multicore
Date Sat, 15 Dec 2012 19:42:13 GMT

    [ https://issues.apache.org/jira/browse/SOLR-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13533124#comment-13533124
] 

Erick Erickson commented on SOLR-1028:
--------------------------------------

I picked a really bad name there, I'll change it. Swappable has nothing to do with swapping
cores via core admin and everything to do with whether there's a limited number of cores that
are loaded at once. "swappable" here means that the system can automatically load/unload cores
as needed to handle the case where there are lots of cores and the installation can tolerate
the pain of having cores load on demand and be slow for the first few queries.

There should be no change in behavior as far as the core admin handler "swap" commands no
matter what the value of "swappable" in solr.xml is, it's actually an unrelated concept despite
the name, but I can sure see why it would be confused....

Maybe "cacheable"?

Sorry for the confusion.
                
> Automatic core loading unloading for multicore
> ----------------------------------------------
>
>                 Key: SOLR-1028
>                 URL: https://issues.apache.org/jira/browse/SOLR-1028
>             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: jenkins.jpg, SOLR-1028.patch, SOLR-1028.patch, SOLR-1028_testnoise.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: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message