[
https://issues.apache.org/jira/browse/SOLR-11045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cao Manh Dat updated SOLR-11045:
--------------------------------
Description:
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.
This problem can easily be fixed ( in another issue ) if the new replica have
same name and coreName like the old one.
was:
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.
This problem can easily be fixed ( in another issue ) if the new replica have
same name and coreName like the old one.
> 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
>
> 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.
> This problem can easily be fixed ( in another issue ) if the new replica have
> same name and coreName like 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]
