[
https://issues.apache.org/jira/browse/SOLR-11970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett resolved SOLR-11970.
--------------------------------------
Resolution: Duplicate
maxShardsPerNode has been removed in SOLR-12847.
> Deprecate maxShardsPerNode while creating collections
> -----------------------------------------------------
>
> Key: SOLR-11970
> URL: https://issues.apache.org/jira/browse/SOLR-11970
> Project: Solr
> Issue Type: Improvement
> Reporter: Varun Thacker
> Assignee: Varun Thacker
> Priority: Major
>
> Today maxShardsPerNode helps users ensure multiple replicas of the same shard
> don't get assigned to the same node.
> Starting 7.0 , the policy framework can express the same constraint.
> Both can conflict today.
> If a user creates a collection with maxShardsPerNode=1 here's the equivalent
> of it in the policy framework.
> {code}
> {"replica": "<2", "shard": "#EACH", "node": "#ANY"}
> {code}
> http://lucene.apache.org/solr/guide/solrcloud-autoscaling-policy-preferences.html#limit-replica-placement
> We should also change the default of maxShardsPerNode from 1 to -1 so that it
> doesn't fail commands when a user doesn't specify this parameter.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
