[
https://issues.apache.org/jira/browse/SOLR-11083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132075#comment-18132075
]
Nick Shanin commented on SOLR-11083:
------------------------------------
>From code reading against apache/main b73f03976fa, MoveReplica deletes the
>replica
>(solr/core/src/java/org/apache/solr/cloud/api/collections/MoveReplicaCmd.java:189-190)
> before adding the new one (MoveReplicaCmd.java:252), with no persisted state
>in between. An interruption between the two leaves the replica count reduced.
>Is this still a concern for shared-filesystem moves?
🤖 AI-generated 🤖
> MoveReplica API can lose replicas for shared file systems on overseer restart
> if source node is live
> ----------------------------------------------------------------------------------------------------
>
> Key: SOLR-11083
> URL: https://issues.apache.org/jira/browse/SOLR-11083
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Priority: Major
>
> MoveReplica unloads the old replica and creates a new one for shared file
> systems. But if the overseer restarts between the two operations then the old
> replica is lost. It is upto the user to detect the failure (using request
> status API) and retry.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
