lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From no...@apache.org
Subject lucene-solr:jira/solr-10821: SOLR-10821: added documentation of collection-policy overriding cluster-policy
Date Mon, 07 Aug 2017 14:50:29 GMT
Repository: lucene-solr
Updated Branches:
  refs/heads/jira/solr-10821 4a8eb9491 -> b0e9527ee


SOLR-10821: added documentation of collection-policy overriding cluster-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/b0e9527e
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/b0e9527e
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/b0e9527e

Branch: refs/heads/jira/solr-10821
Commit: b0e9527eea5d2b6da903ddfc0c5d4d19230145e0
Parents: 4a8eb94
Author: Noble Paul <noble@apache.org>
Authored: Tue Aug 8 00:20:20 2017 +0930
Committer: Noble Paul <noble@apache.org>
Committed: Tue Aug 8 00:20:20 2017 +0930

----------------------------------------------------------------------
 .../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/b0e9527e/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 f8bbb92..7c3674e 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. Also, if `maxShardsPerNode` is specified during the time of collection
creation then both `maxShardsPerNode` and the policy rules must be satisfied.
+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. But it is possible to override conditions specified in cluster-policy
using collection-specific policy. For example, if a clause `{replica: '<3',node:'#ANY'}`
is present in cluster-policy and the collection-specific policy has a clause `{replica: '<4',node:'#ANY'}`
, the cluster policy is ignored in favor of the collection policy . 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