[
https://issues.apache.org/jira/browse/SOLR-12214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16434958#comment-16434958
]
ASF subversion and git services commented on SOLR-12214:
--------------------------------------------------------
Commit 11d54b0cc4fd1df567afe9f4690e0f5a8a55f1ab in lucene-solr's branch
refs/heads/master from [~caomanhdat]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=11d54b0 ]
SOLR-12214: Leader may skip publish itself as ACTIVE even 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: [email protected]
For additional commands, e-mail: [email protected]
