[
https://issues.apache.org/jira/browse/SOLR-5146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031050#comment-17031050
]
David Smiley commented on SOLR-5146:
------------------------------------
{quote}...but then it's not immediately possible for it to get the shard leader
election done since other nodes are not currently participating for that slice.
{quote}
I don't get what you are saying here. The "trick" with transient cores with
SolrCloud will be that SolrCloud needn't know about the loaded status. Maybe
there will be an exception but it'll be a secret inside the node (other
nodes/replicas won't know). The core is _present_, and thus it's leader status
is whatever it is to SolrCloud. It might be awoken to participate in
leadership elections (I hope not) but if so I'll look to fix that so an
unloaded core can stay that way during this. If there is data to sync then the
core will be awoken to do so (/update and /replication and all request handlers
require the core be loaded).
> 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
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
