[jira] [Commented] (SOLR-11970) Deprecate maxShardsPerNode while creating collections

["Varun Thacker (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-11970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16650312#comment-16650312 ] 

Varun Thacker commented on SOLR-11970:
--------------------------------------

[~shalinmangar] after the recent changes going into 7.6 ( SOLR-12739 and linked Jiras ) this issue can perhaps be closed as invalid?

> 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
>            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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org