[jira] [Commented] (SOLR-11083) MoveReplica API can lose replicas for shared file systems on overseer restart if source node is live

["Shalin Shekhar Mangar (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-11083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087036#comment-16087036 ] 

Shalin Shekhar Mangar commented on SOLR-11083:
----------------------------------------------

The same problem does not apply for non-shared filesystems because for them, MoveReplica first creates a new replica and then tries to delete the old core. So even if overseer fails in between, the cluster just ends up with an extra replica.

> 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
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: hdfs, SolrCloud
>            Reporter: Shalin Shekhar Mangar
>             Fix For: 7.1
>
>
> 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
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org