Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
-
None
Description
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.
{"replica": "<2", "shard": "#EACH", "node": "#ANY"}
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.
Attachments
Issue Links
- duplicates
-
SOLR-12847 Cut over implementation of maxShardsPerNode to a collection policy
-
- Closed
-