[
https://issues.apache.org/jira/browse/SOLR-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960511#comment-14960511
]
Yee commented on SOLR-3940:
---------------------------
this seems happened in solr5.2.1
> Rejoining the leader election incorrectly triggers the code path for a fresh
> cluster start rather than fail over.
> -----------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-3940
> URL: https://issues.apache.org/jira/browse/SOLR-3940
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Minor
> Labels: 4.0.1_Candidate
> Fix For: 4.1, Trunk
>
>
> A rejoin may happen when a node decides it may not be the best leader
> candidate.
> This means that in certain fail over situations, the new leader election may
> wait until a timeout expires before proceeding - instead, there should be no
> wait because the we should not expect that the leader that went down is
> coming back anytime soon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
