lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sha...@apache.org
Subject lucene-solr:jira/solr-10821: SOLR-10821: Added note on using maxShardsPerNode along with a policy
Date Fri, 04 Aug 2017 09:06:09 GMT
Repository: lucene-solr
Updated Branches:
  refs/heads/jira/solr-10821 2a9bb140e -> 4a8eb9491


SOLR-10821: Added note on using maxShardsPerNode along with a policy


Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
Commit: http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/4a8eb949
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/4a8eb949
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/4a8eb949

Branch: refs/heads/jira/solr-10821
Commit: 4a8eb9491a1dc8099805656adec34197d0dab092
Parents: 2a9bb14
Author: Shalin Shekhar Mangar <shalin@apache.org>
Authored: Fri Aug 4 14:35:57 2017 +0530
Committer: Shalin Shekhar Mangar <shalin@apache.org>
Committed: Fri Aug 4 14:35:57 2017 +0530

----------------------------------------------------------------------
 .../src/solrcloud-autoscaling-policy-preferences.adoc              | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a8eb949/solr/solr-ref-guide/src/solrcloud-autoscaling-policy-preferences.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/solrcloud-autoscaling-policy-preferences.adoc b/solr/solr-ref-guide/src/solrcloud-autoscaling-policy-preferences.adoc
index f7e92c0..f8bbb92 100644
--- a/solr/solr-ref-guide/src/solrcloud-autoscaling-policy-preferences.adoc
+++ b/solr/solr-ref-guide/src/solrcloud-autoscaling-policy-preferences.adoc
@@ -193,7 +193,7 @@ Place all replicas in nodes with freedisk more than 500GB when possible.
Here we
 
 By default, the cluster policy, if it exists, is used automatically for all collections in
the cluster. However, we can create named policies which can be attached to a collection at
the time of its creation by specifying the policy name along with a `policy` parameter.
 
-When a collection-specific policy is used, the rules in that policy are appended to the rules
in the cluster policy and the combination of both are used. Therefore, it is recommended that
you do not add rules to collection-specific policy that conflict with the ones in the cluster
policy. Doing so will disqualify all nodes in the cluster from matching all criteria and make
the policy useless.
+When a collection-specific policy is used, the rules in that policy are appended to the rules
in the cluster policy and the combination of both are used. Therefore, it is recommended that
you do not add rules to collection-specific policy that conflict with the ones in the cluster
policy. Doing so will disqualify all nodes in the cluster from matching all criteria and make
the policy useless. Also, if `maxShardsPerNode` is specified during the time of collection
creation then both `maxShardsPerNode` and the policy rules must be satisfied.
 
 Some attributes such as `cores` can only be used in the cluster policy.
 


Mime
View raw message