[SOLR-1028] Automatic core loading unloading for multicore

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0, 6.0
• Fix Version/s: 4.1, 6.0
• Component/s: multicore
• Assignee: Erick Erickson
• Reporter: Noble Paul
• Created: 20/Feb/09 04:38
• Updated: 09/May/16 18:43
• Resolved: 13/Jan/13 13:12

Description

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

Issue Links

• blocks: SOLR-1293 Support for large no:of cores and faster loading/unloading of cores
• depends upon: SOLR-880 SolrCore should have a a lazy startup option
• is related to: SOLR-4268 Admin UI - button to unload transient core without removing from solr.xml
• relates to: SOLR-4300 Possible race condition in CoreContainer.getCore() when lazily loading cores.
• relates to: SOLR-4149 Lazy core test occasionally fails.
• relates to: SOLR-4196 Untangle XML-specific nature of Config and Container classes
• relates to: SOLR-4229 "Swappable" (introduced in 1028) is confusing. Change the name
• supercedes: SOLR-1530 Open IndexSearcher lazily