-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
None
-
Service Arch
-
Fully Compatible
-
2024-08-20
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
To match the current behavior, the ShardingTaskExecutorPoolReplicaSetMatching setting should only be configured for mongos processes. The sets_replica_set_matching_strategy resmoke test tag exclusion can be disregarded because it is not applicable to jstests/core/ and jstests/concurrency/ tests which do not spawn their own MongoDB clusters.
- ~ Enterprise RHEL 8 (with {ShardingTaskExecutorPoolReplicaSetMatching: "matchPrimaryNode"}) (link)
- ~ Enterprise RHEL 8 (with {ShardingTaskExecutorPoolReplicaSetMatching: "matchBusiestNode"}) (link)
- ~ Enterprise RHEL 8 (with {ShardingTaskExecutorPoolReplicaSetMatching: "disabled"}) (link)
The default value of --setParameter ShardingTaskExecutorPoolReplicaSetMatching="automatic" corresponds to "matchPrimaryNode" on mongos can be omitted from the config fuzzer choices.
- is related to
-
SERVER-53393 Add EVG variant[s] for ShardingTaskExecutorPoolReplicaSetMatching
-
- Closed
-