[
https://issues.apache.org/jira/browse/SOLR-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855281#comment-13855281
]
ASF subversion and git services commented on SOLR-5568:
-------------------------------------------------------
Commit 1553031 from [~markrmil...@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 SolrCore cannot decide to be the leader just because the cluster state says
> no other SolrCore's are active.
> -------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-5568
> URL: https://issues.apache.org/jira/browse/SOLR-5568
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 5.0, 4.7, 4.6.1
>
>
> This is a problem on cluster startup for one, and a little scary with stale
> cluster state for another. I thought I had removed it before.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
