You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by is...@apache.org on 2020/07/20 13:20:34 UTC
[lucene-solr] branch master updated: SOLR-14656: Adding back
REPLACENODE documentation that was omitted by mistake
This is an automated email from the ASF dual-hosted git repository.
ishan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/lucene-solr.git
The following commit(s) were added to refs/heads/master by this push:
new b46321e SOLR-14656: Adding back REPLACENODE documentation that was omitted by mistake
b46321e is described below
commit b46321e19e2bea1981c5a22a9db4d9236a06f146
Author: Ishan Chattopadhyaya <is...@apache.org>
AuthorDate: Mon Jul 20 18:50:19 2020 +0530
SOLR-14656: Adding back REPLACENODE documentation that was omitted by mistake
---
solr/solr-ref-guide/src/cluster-node-management.adoc | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/solr/solr-ref-guide/src/cluster-node-management.adoc b/solr/solr-ref-guide/src/cluster-node-management.adoc
index b930db6..fbd0fc6 100644
--- a/solr/solr-ref-guide/src/cluster-node-management.adoc
+++ b/solr/solr-ref-guide/src/cluster-node-management.adoc
@@ -281,6 +281,17 @@ http://localhost:8983/solr/admin/collections?action=BALANCESHARDUNIQUE&collectio
Examining the clusterstate after issuing this call should show exactly one replica in each shard that has this property.
+[[replacenode]]
+== REPLACENODE: Move All Replicas in a Node to Another
+
+This command recreates replicas in one node (the source) to another node(s) (the target). After each replica is copied, the replicas in the source node are deleted.
+
+For source replicas that are also shard leaders the operation will wait for the number of seconds set with the `timeout` parameter to make sure there's an active replica that can become a leader either an existing replica becoming a leader or the new replica completing recovery and becoming a leader).
+
+The API uses the Autoscaling framework to find nodes that can satisfy the disk requirements for the new replicas but only when an Autoscaling policy is configured. Refer to <solrcloud-autoscaling-policy-preferences.adoc#solrcloud-autoscaling-policy-preferences,Autoscaling Policy and Preferences>> section for more details.
+
+`/admin/collections?action=REPLACENODE&sourceNode=_source-node_&targetNode=_target-node_`
+
=== REPLACENODE Parameters
`sourceNode`::