[
https://issues.apache.org/jira/browse/SOLR-12110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16403137#comment-16403137
]
ASF subversion and git services commented on SOLR-12110:
--------------------------------------------------------
Commit 8a3742d2ee342ee60a6ed822e36fbdf66e0b5b97 in lucene-solr's branch
refs/heads/branch_7_3 from [~caomanhdat]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=8a3742d ]
SOLR-12110: Replica which failed to register in Zk can become leader
> Replica which failed to register in Zk can become leader
> --------------------------------------------------------
>
> Key: SOLR-12110
> URL: https://issues.apache.org/jira/browse/SOLR-12110
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 7.3
> Reporter: Cao Manh Dat
> Assignee: Cao Manh Dat
> Priority: Blocker
> Fix For: 7.3
>
> Attachments: SOLR-12110.patch, SOLR-12110.patch
>
>
> In case of when an exception is thrown in ZkController.register() a replica
> can still be able to joinElection and become leader after that. This will
> cause many problems, one of the problems can happen (the patch including a
> test which lead to this failure) is
> A replica with DOWN state can become a leader and the shard will be stuck in
> this state forever until the replica is removed or the node contains the
> replica is restarted.
> This won't be a problem in Solr 7.2.1 because a replica with last published
> state = DOWN can't become a leader, only since SOLR-7034 get resolved (by
> SOLR-12011)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
