[
https://issues.apache.org/jira/browse/SOLR-9223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132105#comment-18132105
]
Nick Shanin commented on SOLR-9223:
-----------------------------------
>From code reading against apache/main b73f03976fa, SOLR-7065 (Closed, Fixed
>7.3/8.0) covers the case where a lower-term replica becomes leader after the
>wait
>(solr/core/src/java/org/apache/solr/cloud/ShardLeaderElectionContext.java:185-188,
> 340-360). The remaining case is the FORCELEADER path. Can this close as fixed
>by SOLR-7065?
🤖 AI-generated 🤖
> Unable to create a shard leader if only a recovering node has the latest
> updates
> --------------------------------------------------------------------------------
>
> Key: SOLR-9223
> URL: https://issues.apache.org/jira/browse/SOLR-9223
> Project: Solr
> Issue Type: Bug
> Reporter: Noble Paul
> Assignee: Noble Paul
> Priority: Major
>
> We ended up with a leaderless shard in the following scenario
> 1) Add a new replica to a shard
> 2) while the node is still recovering do indexing
> 3) Delete the replica that is the leader of the shard
> It's likely that the latest update(s) is only sent to the node that is
> recovering. Other nodes try to become the leader but they can't because they
> don't have the latest updates. The node that has the latest updates is trying
> to recover. And we end up in a situation where the shard does not have a
> leader.
> How do we resolve this problem? Any suggestions [[email protected]]
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
