[ https://issues.apache.org/jira/browse/SOLR-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610679#comment-13610679
]
Commit Tag Bot commented on SOLR-3940:
--------------------------------------
[branch_4x commit] Mark Robert Miller
http://svn.apache.org/viewvc?view=revision&revision=1397672
SOLR-3939: Consider a sync attempt from leader to replica that fails due to 404 a success.
SOLR-3940: Rejoining the leader election incorrectly triggers the code path for a fresh cluster
start rather than fail over.
> 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, 5.0
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org