[
https://issues.apache.org/jira/browse/SOLR-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232537#comment-17232537
]
David Smiley commented on SOLR-6399:
------------------------------------
Assuming you are using docValues on appropriate fields (e.g. fields you facet,
sort, group, custom relevancy calcs), and that you are using Solr 8+, most of
the memory associated with each core is memory-mapped, and will be paged out by
the OS if you are not using it. If you have thousands of cores, then this
isn't good enough. I think the right solution is "transient cores" to be
compatible with SolrCloud -- SOLR-5146 which isn't resolved.
> Implement unloadCollection in the Collections API
> -------------------------------------------------
>
> Key: SOLR-6399
> URL: https://issues.apache.org/jira/browse/SOLR-6399
> Project: Solr
> Issue Type: New Feature
> Reporter: dfdeshom
> Priority: Major
> Fix For: 6.0
>
>
> There is currently no way to unload a collection without deleting its
> contents. There should be a way in the collections API to unload a collection
> and reload it later, as needed.
> A use case for this is the following: you store logs by day, with each day
> having its own collection. You are required to store up to 2 years of data,
> which adds up to 730 collections. Most of the time, you'll want to have 3
> days of data loaded for search. Having just 3 collections loaded into memory,
> instead of 730 will make managing Solr easier.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
