Varun Thacker created SOLR-11970:
------------------------------------
Summary: Deprecate maxShardsPerNode while creating collections
Key: SOLR-11970
URL: https://issues.apache.org/jira/browse/SOLR-11970
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Varun Thacker
Assignee: Varun Thacker
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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
