[
https://issues.apache.org/jira/browse/SOLR-11045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16085270#comment-16085270
]
ASF subversion and git services commented on SOLR-11045:
--------------------------------------------------------
Commit fc20ed399c2e88843087ef8f0c35146ba414c410 in lucene-solr's branch
refs/heads/branch_7_0 from [~caomanhdat]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=fc20ed3 ]
SOLR-11045: The new replica created by MoveReplica will have to have same name
and coreName as the old one in case of HDFS
> 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
> Fix For: 7.0
>
> Attachments: SOLR-11045.patch, 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: [email protected]
For additional commands, e-mail: [email protected]
