lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject lucene-solr:master: SOLR-9743: documentation
Date Fri, 08 Dec 2017 08:55:42 GMT
Repository: lucene-solr
Updated Branches:
  refs/heads/master b32739428 -> 25f24e094

SOLR-9743: documentation


Branch: refs/heads/master
Commit: 25f24e094e8c7d47356ed15ab5957e3fb7e2bec8
Parents: b327394
Author: Noble Paul <>
Authored: Fri Dec 8 19:30:57 2017 +1100
Committer: Noble Paul <>
Committed: Fri Dec 8 19:55:27 2017 +1100

 solr/solr-ref-guide/src/collections-api.adoc | 11 +++++++++++
 1 file changed, 11 insertions(+)
diff --git a/solr/solr-ref-guide/src/collections-api.adoc b/solr/solr-ref-guide/src/collections-api.adoc
index 4879175..784e2cf 100644
--- a/solr/solr-ref-guide/src/collections-api.adoc
+++ b/solr/solr-ref-guide/src/collections-api.adoc
@@ -1912,6 +1912,17 @@ The name of the destination node. This parameter is required.
 Request ID to track this action which will be <<Asynchronous Calls,processed asynchronously>>.
+== UTILIZENODE: Utilize a new node
+This command can be used to move some replicas from the existing nodes to a new node or lightly
loaded node and reduce the load on them. This uses your autoscaling policies and preferences
to identify which replica needs to be moved. It tries to fix any policy violations first and
then it tries to move some load off of the most loaded nodes according to the preferences.
+=== UTILIZENODE Parameters
+`node`:: The name of the node that needs to be utilized. This parameter is required
 == Asynchronous Calls
 Since some collection API calls can be long running tasks (such as SPLITSHARD), you can optionally
have the calls run asynchronously. Specifying `async=<request-id>` enables you to make
an asynchronous call, the status of which can be requested using the <<requeststatus,REQUESTSTATUS>>
call at any time.

View raw message