You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2012/10/12 20:35:04 UTC

[jira] [Updated] (SOLR-3940) Rejoining the leader election incorrectly triggers the code path for a fresh cluster start rather than fail over.

     [ https://issues.apache.org/jira/browse/SOLR-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Miller updated SOLR-3940:
------------------------------

    Labels: 4.0.1_Candidate  (was: )
    
> 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.0.1, 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