[
https://issues.apache.org/jira/browse/SOLR-9320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385323#comment-15385323
]
Nitin Sharma commented on SOLR-9320:
------------------------------------
Clarification on this. When you mean recreate, does the naming matter? Lets say
x_shard1_replica1 is on source node, if you want to move it to destination
node, we can
a) either create a new replica (x_shard1_replica2) and delete the source. That
will leave uneven naming conventions in the cluster. (there will not be a
replica1 but a replica2).
b) Preserve the exact same name as the replica in source node. We can achieve
this by creating a temp replica on destination first, deleting the replica on
source, recreating the replica (with same name) on destination and then
cleaning up the temp.
Option (b) can be thought of as a migrate core.
Let me know which sounds more usable.
> A REPLACENODE command to decommission an existing node with another new node
> ----------------------------------------------------------------------------
>
> Key: SOLR-9320
> URL: https://issues.apache.org/jira/browse/SOLR-9320
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Reporter: Noble Paul
> Fix For: 6.1
>
>
> The command should accept a source node and target node. recreate the
> replicas in source node in the target and do a DLETENODE of source node
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
