Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-53394

Make ShardingTaskExecutorPoolReplicaSetMatching default to disabled for MongoD

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Critical - P2
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.9.0, 4.2.13, 4.4.5
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.4, v4.2
    • Sprint:
      Service Arch 2021-02-08
    • Case:

      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

          Task - A task that needs to be done. DOCS-14167 Investigate changes in SERVER-53394: Make ShardingTaskExecutorPoolReplicaSetMatching default to disabled for MongoD

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              george.wangensteen George Wangensteen
              Reporter:
              ben.caimano Benjamin Caimano (Inactive)
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: