[
https://issues.apache.org/jira/browse/SOLR-12739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16639832#comment-16639832
]
Shalin Shekhar Mangar commented on SOLR-12739:
----------------------------------------------
One major block to using autoscaling as default is that we do not permit
specifying maxShardsPerNode during collection creation if a policy is
configured. Although if a collection already exists with maxShardsPerNode and a
policy is configured then we try to do the right thing which is to respect both
maxShardsPerNode and the policy itself. Our documentation also says the same
thing. So I think the restriction of not accepting a maxShardsPerNode is not
useful. We should accept it and do what we do for old existing collections. I
have made this change in my latest patch.
> Make autoscaling policy based replica placement the default strategy for
> placing replicas
> -----------------------------------------------------------------------------------------
>
> Key: SOLR-12739
> URL: https://issues.apache.org/jira/browse/SOLR-12739
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling, SolrCloud
> Reporter: Shalin Shekhar Mangar
> Priority: Major
> Fix For: 7.6, master (8.0)
>
> Attachments: SOLR-12739.patch, SOLR-12739.patch, SOLR-12739.patch
>
>
> Today the default placement strategy is the same one used since Solr 4.x
> which is to select nodes on a round robin fashion. I propose to make the
> autoscaling policy based replica placement as the default policy for placing
> replicas.
> This is related to SOLR-12648 where even though we have default cluster
> preferences, we don't use them unless a policy is also configured.
--
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
