Make ShardingTaskExecutorPoolReplicaSetMatching default to disabled for MongoD

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Critical - P2
    • 4.9.0, 4.2.13, 4.4.5
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • v4.4, v4.2
    • Service Arch 2021-02-08
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              George Wangensteen (Inactive)
              Reporter:
              Benjamin Caimano (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: