[
https://issues.apache.org/jira/browse/SOLR-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950591#comment-15950591
]
Ishan Chattopadhyaya commented on SOLR-10239:
---------------------------------------------
In terms of design, I had couple of options in mind.
# ADDREPLICA on target node, followed by DELETEREPLICA on source node.
# Create a core on target node, fetch index from source node, then sync/recover
with leader, finally DELETEREPLICA on source node.
The former is simpler to build. The latter potentially exerts less pressure on
the leader. [~noble.paul], [~shalinmangar], [~caomanhdat], what do you think?
> MOVEREPLICA API
> ---------------
>
> Key: SOLR-10239
> URL: https://issues.apache.org/jira/browse/SOLR-10239
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Ishan Chattopadhyaya
> Assignee: Cao Manh Dat
>
> To move a replica from a node to another node, there should be an API
> command. This should be better than having to do ADDREPLICA and DELETEREPLICA.
> The API will like this
> {code}
> /admin/collections?action=MOVEREPLICA&collection=collection&shard=shard&replica=replica&node=nodeName&toNode=nodeName
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
