-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
CAR Team 2025-11-10, CAR Team 2025-11-24, CAR Team 2025-12-08
-
1
-
🟩 Routing and Topology
-
None
-
None
-
None
-
None
-
None
-
None
In the following add/remove shard suites, we have random balancing enabled:
- aggregation_unsplittable_collections_on_random_shard_passthrough_with_config_transitions_and_add_remove_shard
- *concurrency_sharded*with_config_transitions_and_add_remove_shard
- jstestfuzz_sharded_with_config_transitions_and_add_remove_shard
In these, though, we have random balancing disabled:
- sharding_jscore_passthrough_with_config_transitions_and_add_remove_shard
- sharded_collections_jscore_passthrough_with_config_transitions_and_add_remove_shard
We should investigate whether we can enable random balancing in those 2 passthrough suites as having this enabled makes it more likely that an added shard is actually used.
- related to
-
SERVER-114065 Test failure in array_index_and_nonIndex_consistent.js due to shard order dependency
-
- Backlog
-