You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Noble Paul (JIRA)" <ji...@apache.org> on 2015/11/04 10:26:27 UTC
[jira] [Commented] (SOLR-7989) Down replica elected leader, stays
down after successful election
[ https://issues.apache.org/jira/browse/SOLR-7989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989195#comment-14989195 ]
Noble Paul commented on SOLR-7989:
----------------------------------
Send the state=ACTIVE first before the LEADER msg
Let's check if the node is actually active before sending the state=ACTIVE message
> Down replica elected leader, stays down after successful election
> -----------------------------------------------------------------
>
> Key: SOLR-7989
> URL: https://issues.apache.org/jira/browse/SOLR-7989
> Project: Solr
> Issue Type: Bug
> Reporter: Ishan Chattopadhyaya
> Attachments: DownLeaderTest.java, DownLeaderTest.java, SOLR-7989.patch
>
>
> It is possible that a down replica gets elected as a leader, and that it stays down after the election.
> Here's how I hit upon this:
> * There are 3 replicas: leader, notleader0, notleader1
> * Introduced network partition to isolate notleader0, notleader1 from leader (leader puts these two in LIR via zk).
> * Kill leader, remove partition. Now leader is dead, and both of notleader0 and notleader1 are down. There is no leader.
> * Remove LIR znodes in zk.
> * Wait a while, and there happens a (flawed?) leader election.
> * Finally, the state is such that one of notleader0 or notleader1 (which were down before) become leader, but stays down.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org