[
https://issues.apache.org/jira/browse/SOLR-16855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17740643#comment-17740643
]
ASF subversion and git services commented on SOLR-16855:
--------------------------------------------------------
Commit b3883ad19c5413a968d5fbe6e45e605a84c3046c in solr's branch
refs/heads/main from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=b3883ad19c5 ]
SOLR-16855: Add a MigrateReplicas API (#1730)
Also:
- Fix orderedPlacement logic for tied nodes
- Remove stashed weight logic in WeightedNode that is no longer used
> Add a MigrateReplicas API
> -------------------------
>
> Key: SOLR-16855
> URL: https://issues.apache.org/jira/browse/SOLR-16855
> Project: Solr
> Issue Type: Sub-task
> Reporter: Houston Putman
> Priority: Major
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Currently the ReplaceNode API lets us migrate replicas from one node to
> another node. However, users might want to migrate multiple nodes at a time,
> or target a set of nodes instead of a single node. This new API would behave
> like the replaceNode API, but give users more flexibility.
> The new API would use the path POST "/api/cluster/replicas/migrate" (much
> like the balance replicas API), and have the following body:
> {
> {{ "sourceNodes": [], # required}}
> {{ "targetNodes": [],}}
> {{ "waitForFinalState": false,}}
> {{ "async": ""}}
> {{}}}
> "sourceNodes" would be required, and an error would be returned if an empty
> list was given. "targetNodes" would be optional, and default to all liveNodes
> that are not provided in "sourceNodes".
> Eventually we could deprecate the ReplaceNode command, or at least have it be
> a shell on-top-of the MigrateReplicas functionality.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
