You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by no...@apache.org on 2017/12/08 07:20:10 UTC
lucene-solr:branch_7x: SOLR-11359: added documentation
Repository: lucene-solr
Updated Branches:
refs/heads/branch_7x 2f0d5bef2 -> 48c0798b3
SOLR-11359: added documentation
Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
Commit: http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/48c0798b
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/48c0798b
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/48c0798b
Branch: refs/heads/branch_7x
Commit: 48c0798b395f32632f7ac88ab31c6132c13c6dc3
Parents: 2f0d5be
Author: Noble Paul <no...@apache.org>
Authored: Fri Dec 8 17:36:41 2017 +1100
Committer: Noble Paul <no...@apache.org>
Committed: Fri Dec 8 18:19:54 2017 +1100
----------------------------------------------------------------------
.../src/solrcloud-autoscaling-api.adoc | 51 ++++++++++++++++++++
1 file changed, 51 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/48c0798b/solr/solr-ref-guide/src/solrcloud-autoscaling-api.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/solrcloud-autoscaling-api.adoc b/solr/solr-ref-guide/src/solrcloud-autoscaling-api.adoc
index 5a41196..9d53552 100644
--- a/solr/solr-ref-guide/src/solrcloud-autoscaling-api.adoc
+++ b/solr/solr-ref-guide/src/solrcloud-autoscaling-api.adoc
@@ -142,6 +142,57 @@ However, since the first node in the first example had more than 1 replica for a
In the above example the node with port 8983 has two replicas for `shard1` in violation of our policy.
+== Suggestions API ==
+Suggestions are operations recommended by the system according to the policies and preferences the user has set. Note that the suggestions are made only if there are `violations` to the policies and the collection admin operation would use the preferences to identify the target node.
+
+The API is available at `/admin/autocaling/suggestion`
+[source,json]
+----
+{
+ "responseHeader":{
+ "status":0,
+ "QTime":101},
+ "suggestions":[{
+ "type":"violation",
+ "violation":{
+ "collection":"mycoll",
+ "shard":"shard2",
+ "tagKey":"7574",
+ "violation":{ "delta":-1},
+ "clause":{
+ "replica":"0",
+ "shard":"#EACH",
+ "port":7574,
+ "collection":"mycoll"}},
+ "operation":{
+ "method":"POST",
+ "path":"/c/mycoll",
+ "command":{"move-replica":{
+ "targetNode":"192.168.43.37:8983_solr",
+ "replica":"core_node7"}}}},
+ {
+ "type":"violation",
+ "violation":{
+ "collection":"mycoll",
+ "shard":"shard2",
+ "tagKey":"7574",
+ "violation":{ "delta":-1},
+ "clause":{
+ "replica":"0",
+ "shard":"#EACH",
+ "port":7574,
+ "collection":"mycoll"}},
+ "operation":{
+ "method":"POST",
+ "path":"/c/mycoll",
+ "command":{"move-replica":{
+ "targetNode":"192.168.43.37:7575_solr",
+ "replica":"core_node15"}}}}],
+ "WARNING":"This response format is experimental. It is likely to change in the future."}
+----
+
+The operation is an actual API call that can be invoked to remedy the current violation
+
== History API
The history of autoscaling events is available at `/admin/autoscaling/history`. It returns information