[ https://issues.apache.org/jira/browse/SOLR-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15003992#comment-15003992 ]
ASF subversion and git services commented on SOLR-8075: ------------------------------------------------------- Commit 1714204 from [~markrmil...@gmail.com] in branch 'dev/trunk' [ https://svn.apache.org/r1714204 ] SOLR-8075: Fix faulty implementation. > Leader Initiated Recovery should not stop a leader that participated in an > election with all of it's replicas from becoming a valid leader. > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: SOLR-8075 > URL: https://issues.apache.org/jira/browse/SOLR-8075 > Project: Solr > Issue Type: Bug > Reporter: Mark Miller > Assignee: Mark Miller > Fix For: 5.4, Trunk > > Attachments: SOLR-8075.patch, SOLR-8075.patch, SOLR-8075.patch, > SOLR-8075.patch, SOLR-8075.patch, SOLR-8075.patch, SOLR-8075.patch > > > Currently, because of SOLR-8069, all the replicas in a shard can be put into > LIR. > If you restart such a shard, the valid leader will will win the election and > sync with the shard and then be blocked from registering as ACTIVE because it > is in LIR. > I think that is a little wonky because I don't think it even tries another > candidate because the leader that cannot publish ACTIVE does not have it's > election canceled. > While SOLR-8069 should prevent this situation, we should add logic to allow a > leader that can sync with it's full shard to become leader and publish ACTIVE > regardless of LIR. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org