[jira] [Resolved] (SOLR-4159) When we are starting a shard from rest, a leader should not consider it's last published state when deciding if it can be the new leader.

["Mark Miller (JIRA)" <ji...@apache.org>]

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

Mark Miller resolved SOLR-4159.
-------------------------------

    Resolution: Fixed
    
> When we are starting a shard from rest, a leader should not consider it's last published state when deciding if it can be the new leader.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-4159
>                 URL: https://issues.apache.org/jira/browse/SOLR-4159
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.0
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>            Priority: Minor
>             Fix For: 4.1, 5.0
>
>
> This makes it so that if a leader goes down before any replicas sync from it, one of the replicas won't take over. But because we wait a while for known replicas to come up and sync + pick the best leader, we should not need to be so strict in this protection and let a replica take a stab at being the leader - it may have been up to date and was only publishing through recovery phases to find that out.

--
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