[
https://issues.apache.org/jira/browse/SOLR-16855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Houston Putman updated SOLR-16855:
----------------------------------
Description:
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.
was:
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.
> 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
>
> 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: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
