Shalin Shekhar Mangar created SOLR-12847:
--------------------------------------------
Summary: Cut over implementation of maxShardsPerNode to a
collection policy
Key: SOLR-12847
URL: https://issues.apache.org/jira/browse/SOLR-12847
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Components: AutoScaling, SolrCloud
Reporter: Shalin Shekhar Mangar
Fix For: 7.6, master (8.0)
We've back and forth over handling maxShardsPerNode with autoscaling policies
(see SOLR-11005 for history). Now that we've reimplemented support for creating
collections with maxShardsPerNode when autoscaling policy is enabled, we should
re-look at how it is implemented.
I propose that we fold maxShardsPerNode (if specified) to a collection level
policy that overrides the corresponding default in cluster policy (see
SOLR-12845). We'll need to ensure that if maxShardsPerNode is specified then
the user sees neither violations nor corresponding suggestions because of the
default cluster policy.
--
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
