You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Cao Manh Dat (JIRA)" <ji...@apache.org> on 2018/04/12 05:28:00 UTC
[jira] [Updated] (SOLR-12214) Leader may skip publish itself as
ACTIVE even its last published state is DOWN
[ https://issues.apache.org/jira/browse/SOLR-12214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cao Manh Dat updated SOLR-12214:
--------------------------------
Summary: Leader may skip publish itself as ACTIVE even its last published state is DOWN (was: Leader may skip publish itself as ACTIVE when its last published state is DOWN)
> Leader may skip publish itself as ACTIVE even its last published state is DOWN
> ------------------------------------------------------------------------------
>
> Key: SOLR-12214
> URL: https://issues.apache.org/jira/browse/SOLR-12214
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Cao Manh Dat
> Assignee: Cao Manh Dat
> Priority: Major
> Attachments: SOLR-12214.patch
>
>
> Found this problem on beasting LeaderVoteWaitTimeout,
> * a replica publish itself as DOWN on RecoveryStrategy.pingLeader()
> * It won the election (by vote wait timeout) then skipping publish itself as ACTIVE (by looking into clusterstate, its state still ACTIVE).
> * ends up with a leader with DOWN state!
> Therefore, replica should look into both clusterstate and its local last published state on skipping publish itself as ACTIVE
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org