[
https://issues.apache.org/jira/browse/SOLR-8075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15000452#comment-15000452
]
Mark Miller commented on SOLR-8075:
-----------------------------------
Patch with fix.
bq. How can I investigate / reproduce this?
Don't know. Saw it not working on a real cluster.
I also saw the shard get stuck with no proper leader still due to the proper
leader being in LIR. It seems LIR is still a little buggy. Fixing this should
be one step towards alleviating that.
I'm going to work on a test that indexes while restarting the whole cluster and
see if I can reproduce some of those bugs.
> 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
>
>
> 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]
