[
https://issues.apache.org/jira/browse/SOLR-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902551#comment-14902551
]
Mark Miller commented on SOLR-8075:
-----------------------------------
Okay, with this patch, if the proper leader still somehow ends up in LIR, on
restart of the shard, if all replicas participate in an election, it will still
become leader.
I'll open another issue into why this test prevents leadership using a safety
catch in publish. My worry with that is that it won't cancel the election, but
that is a separate issue.
> 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
> Attachments: 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: [email protected]
For additional commands, e-mail: [email protected]
