[
https://issues.apache.org/jira/browse/SOLR-11082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Risden updated SOLR-11082:
--------------------------------
Fix Version/s: (was: 8.1)
(was: master (9.0))
> MoveReplica API for shared file systems should not delete the old replica if
> the source node is not live
> --------------------------------------------------------------------------------------------------------
>
> Key: SOLR-11082
> URL: https://issues.apache.org/jira/browse/SOLR-11082
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: hdfs, SolrCloud
> Reporter: Shalin Shekhar Mangar
> Priority: Major
>
> MoveReplica API for shared file systems attempts to delete the old replica
> and then creates a new replica (with same core and coreNode name) on the
> target node. If the overseer fails between the two operations then the
> replica is lost. The API should detect that if the source is not live, it
> only needs to create the new replica. Then the old replica (upon coming back
> online) auto-detects a replacement and unloads itself. This is also how
> OverseerAutoReplicaFailoverThread works today.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
