[
https://issues.apache.org/jira/browse/SOLR-5146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628863#comment-14628863
]
Erick Erickson commented on SOLR-5146:
--------------------------------------
Right, I can see where that would happen. There are a couple of tickets out
there for handling lots and lots of collections. I'm a little blinded when I
think of lazily-loaded cores by knowing the code. Maybe I'm getting it now....
Hmmmm, I haven't thought this through at all, but picking up on your initial
comment today instead of conflating lazy loading with this issue maybe we could
use the LRU core lists maintained by the lazy core load to periodically reopen
searchers on the oldest N cores. I can't say I have the bandwidth to work on
this, but it seems like what you were thinking.
I'm guessing that in this situation you don't have much autowarming going on,
and that the cache sizes for all your collections is pretty small. If those
assumptions are false lowering them might help.
Interesting use-case though, hadn't thought about that very carefully.
> 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]
