Details
Description
We currently set ShardingTaskExecutorPoolReplicaSetMatching to "matchPrimaryNode" by default for both MongoD and MongoS (see here). However, the "matchPrimaryNode" behavior can be problematic for topologies when multiple shardsvrs experience a rapid influx of cross-shard operations. We should disable this behavior on MongoD nodes but not MongoS nodes.
Attachments
Issue Links
- is documented by
-
DOCS-14167 Investigate changes in SERVER-53394: Make ShardingTaskExecutorPoolReplicaSetMatching default to disabled for MongoD
-
- Closed
-