[jira] [Resolved] (SOLR-5644) SplitShard does not handle not finding a shard leader well.

["Shalin Shekhar Mangar (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shalin Shekhar Mangar resolved SOLR-5644.
-----------------------------------------

    Resolution: Fixed

Thanks Mark and Anshum.

The same getLeaderRetry should be used in migrate action as well. I'll open an issue and fix it.

> SplitShard does not handle not finding a shard leader well.
> -----------------------------------------------------------
>
>                 Key: SOLR-5644
>                 URL: https://issues.apache.org/jira/browse/SOLR-5644
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>            Reporter: Mark Miller
>            Assignee: Anshum Gupta
>            Priority: Minor
>             Fix For: 5.0, 4.7
>
>         Attachments: SOLR-5644.patch, SOLR-5644.patch
>
>
> In OverseerCollectionProcessor:
>     // find the leader for the shard
>     Replica parentShardLeader = clusterState.getLeader(collectionName, slice);
> This returns null if there is no current leader and the following code does not deal with that case and instead NPE's.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org