You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2014/02/07 00:29:19 UTC
[jira] [Commented] (SOLR-5644) SplitShard does not handle not
finding a shard leader well.
[ https://issues.apache.org/jira/browse/SOLR-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893968#comment-13893968 ]
Mark Miller commented on SOLR-5644:
-----------------------------------
I don't think that clusterstate object will ever be updated?
What about changing the splitshard method to take zkstatereader and use zkstatereader#getleaderretry?
> 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
>
>
> 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