[
https://issues.apache.org/jira/browse/SOLR-8629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132065#comment-18132065
]
Nick Shanin commented on SOLR-8629:
-----------------------------------
>From code reading against apache/main b73f03976fa, PeerSync tolerates connect
>errors and 503 or 404 on GET_VERSIONS, but treats other errors as a failed
>sync (solr/core/src/java/org/apache/solr/update/PeerSync.java:370-431). The
>candidate then rejoins the election
>(solr/core/src/java/org/apache/solr/cloud/ShardLeaderElectionContext.java:219,
>244-245). So one replica returning 500 can keep a healthy candidate from
>becoming leader. Is this still the case?
🤖 AI-generated 🤖
> When a prospective leader attempts to sync with it's shard, we should only
> fail the sync due to peer sync, not necessarily other exceptions.
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-8629
> URL: https://issues.apache.org/jira/browse/SOLR-8629
> Project: Solr
> Issue Type: Bug
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Major
>
> Otherwise, one screwed up replica can prevent a leader even if there are 100
> other good replicas.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
