Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
When multiple collection creations are done concurrently with a collection-level policy, multiple replicas of a single shard can end up on the same node, violating the specified policy.
This was observed on both 8.2 and master.
Attachments
Issue Links
- is related to
-
SOLR-10822 Concurrent execution of Policy computations should yield correct result
- Closed
-
SOLR-13891 Default replica placement is random
- Resolved
-
SOLR-14347 Autoscaling placement wrong when concurrent replica placements are calculated
- Closed
- links to