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

Scott Blum commented on SOLR-5146:
----------------------------------

We have a multi-tenant model ourselves (collection per tenant), but our indexes 
are large enough to warrant sharding and replication for performance and 
durability.  The problem we have is that once a core has been active and filled 
its cache, that memory is tied up forever.  It's sort of a 
tragedy-of-the-commons with no one overseeing global caching / memory usage.  
Over time, the heap low water mark rises indefinitely until VM death.

Our current best idea, absent a real solution, is to periodically reload all 
cores, just to force all the caches to empty out.  This resets the heap low 
water mark back to a reasonable level.  So anything that would make things even 
incrementally better would be a win for us.

> Figure out what it would take for lazily-loaded cores to play nice with 
> SolrCloud
> ---------------------------------------------------------------------------------
>
>                 Key: SOLR-5146
>                 URL: https://issues.apache.org/jira/browse/SOLR-5146
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>    Affects Versions: 4.5, Trunk
>            Reporter: Erick Erickson
>            Assignee: Shalin Shekhar Mangar
>             Fix For: Trunk
>
>
> The whole lazy-load core thing was implemented with non-SolrCloud use-cases 
> in mind. There are several user-list threads that ask about using lazy cores 
> with SolrCloud, especially in multi-tenant use-cases.
> This is a marker JIRA to investigate what it would take to make lazy-load 
> cores play nice with SolrCloud. It's especially interesting how this all 
> works with shards, replicas, leader election, recovery, etc.
> NOTE: This is pretty much totally unexplored territory. It may be that a few 
> trivial modifications are all that's needed. OTOH, It may be that we'd have 
> to rip apart SolrCloud to handle this case. Until someone dives into the 
> code, we don't know.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to