[SOLR-12847] Cut over implementation of maxShardsPerNode to a collection policy

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: master (9.0), 8.2
• Component/s: AutoScaling, SolrCloud
• Assignee: Unassigned
• Reporter: Shalin Shekhar Mangar
• Created: 09/Oct/18 08:12
• Updated: 08/Jun/19 15:01

Description

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.

Issue Links

• relates to: SOLR-13248 Autoscaling based replica placement is broken out of the box