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.