lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson (JIRA)" <>
Subject [jira] [Commented] (SOLR-1028) Automatic core loading unloading for multicore
Date Sun, 28 Oct 2012 17:57:12 GMT


Erick Erickson commented on SOLR-1028:

Here are the comments I _meant_ to include.

1> implementa loadOnStartup (default true) as a <core...> attribute. Causes the core
to be loaded when Solr starts, just like it does now.
2> implements swappable (default false) as a <core...> attribute. Allows Solr to
automatically unload the core if it runs out of room in a (new) LRU core list.
3> implements a swappableCacheSize attribute for <cores...> (default unlimited) for
how large the list of "swappable" cores can grow to before they're closed and swapped out.
4> Wraps a bunch of exceptions in CoreContainer into a SolrException (as per comments in
that code).
5> persists these two new <core> attributes. 
6> persists the swappableCacheSize attribute of <cores> if set.

All the tests run, so it'll be interesting to see what the build machine thinks. In all its

The cost of this functionality in the usual case (i.e. for current users) is, I believe, only
a single check in CoreContainer.getCore when the core name isn't already found in the usual"

> Automatic core loading unloading for multicore
> ----------------------------------------------
>                 Key: SOLR-1028
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: multicore
>            Reporter: Noble Paul
>            Assignee: Erick Erickson
>             Fix For: 4.1
>         Attachments: 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