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

ASF subversion and git services commented on SOLR-13955:
--------------------------------------------------------

Commit 947241cded534078a66fc7789069064c90cbc012 in lucene-solr's branch 
refs/heads/jira/SOLR-13101 from Bilal Waheed
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=947241c ]

SOLR-13955: Fixed issues with SHARED core descriptor ZK discovery (#1027)

-Handled a case where replicas for a node can be null.
-Prefer core loading over discovery errors.
-Make sure discovered core descriptor is persisted.
-Added missing properties. Unit test to ensure that we do not miss anything.
-Added test to index on discovered core.
-Added a fail fast for indexing pipeline when processing a non-shared replica 
for shared collection
-Removed the obsolete comments from CorePullTask#createCore.
-Renamed SimpleSharedStoreMissingCorePullTest.java to 
SharedStoreMissingCoreTest.java

> SHARED replicas can recover on clean disk
> -----------------------------------------
>
>                 Key: SOLR-13955
>                 URL: https://issues.apache.org/jira/browse/SOLR-13955
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud
>            Reporter: Bilal Waheed
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> One of the benefits of SHARED replica is that it provides the ability to run 
> SolrCloud with ephemeral disk(containers). Since the source of truth is in 
> shared store, we can safely recover index from there. But currently there is 
> no support to reason about the core descriptors that do not live locally on 
> the disk. The purpose of this task is to discover missing core descriptors 
> for SHARED replicas from ZK.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to