You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2020/03/25 15:29:00 UTC
[jira] [Updated] (SOLR-5146) Figure out what it would take for
lazily-loaded cores to play nice with SolrCloud
[ https://issues.apache.org/jira/browse/SOLR-5146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley updated SOLR-5146:
-------------------------------
Labels: scaling (was: )
Just a status update: I have something working but only for the "shared" (i.e. shared storage) replica types – SOLR-13101. Standard replicas (NRT) are harder to support because of PeerSync/replication that can interfere with core unloading if both should happen at the same time. It can probably be figured out but I'm punting on that indefinitely. Once "shared" replicas is merged then I can show a PR here. There isn't that much to it actually.
loadOnStartup=false is not as easy as I had hoped because of standard replica type steps including PeerSync that necessitate core loading. It should be achievable with "shared" replicas, though.
> 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, 6.0
> Reporter: Erick Erickson
> Assignee: David Smiley
> Priority: Major
> Labels: scaling
>
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org