You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Ilan Ginzburg (Jira)" <ji...@apache.org> on 2020/02/05 19:02:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17030919#comment-17030919 ] 

Ilan Ginzburg commented on SOLR-5146:
-------------------------------------

Isn't a fundamental difference in SolrCloud vs standalone Solr that if we assume a given slice (shard) is not loaded anywhere and a request is received by a node for it, the node can load/open its local copy of that core just fine (let's assume that since it works in standalone), 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.

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org