You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/12/22 22:17:50 UTC
[jira] [Commented] (SOLR-5569) A replica should not try and recover
from a leader until it has published that it is ACTIVE.
[ https://issues.apache.org/jira/browse/SOLR-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855280#comment-13855280 ]
ASF subversion and git services commented on SOLR-5569:
-------------------------------------------------------
Commit 1553031 from [~markrmiller@gmail.com] in branch 'dev/trunk'
[ https://svn.apache.org/r1553031 ]
SOLR-5552: Leader recovery process can select the wrong leader if all replicas for a shard are down and trying to recover as well as lose updates that should have been recovered.
SOLR-5569 A replica should not try and recover from a leader until it has published that it is ACTIVE.
SOLR-5568 A SolrCore cannot decide to be the leader just because the cluster state says no other SolrCore's are active.
> A replica should not try and recover from a leader until it has published that it is ACTIVE.
> --------------------------------------------------------------------------------------------
>
> Key: SOLR-5569
> URL: https://issues.apache.org/jira/browse/SOLR-5569
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Critical
> Fix For: 5.0, 4.7, 4.6.1
>
>
> The leader may be in the middle of a tran log replay which means those updates coming in are not distributed and a pre replication commit could be ignored.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org