[ https://issues.apache.org/jira/browse/SOLR-11045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cao Manh Dat updated SOLR-11045: -------------------------------- Attachment: SOLR-11045.patch Thank [~shalinmangar], this patch fix all problems mentioned. > The new replica created by MoveReplica will have to have same name and > coreName as the old one in case of HDFS > -------------------------------------------------------------------------------------------------------------- > > Key: SOLR-11045 > URL: https://issues.apache.org/jira/browse/SOLR-11045 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Reporter: Cao Manh Dat > Assignee: Cao Manh Dat > Attachments: SOLR-11045.patch, SOLR-11045.patch > > > Currently, if the node contains a replica ( the replica being moved ) go > down, then we call moveReplica command for it. That replica will only be > removed from states.json. So If that node come back, we will have 2 replicas > point to the same dataDir in HDFS. > So if moveReplica can maintain the same name and coreName for the new > replica, we can reuse {{CloudUtil.checkSharedFSFailoverReplaced()}} to clean > the old one. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org