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

Fix mongos_large_catalog_workloads NetworkInterfaceExceededTimeLimit error

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 4.4.0
    • Component/s: Sharding
    • None
    • Cluster Scalability
    • Service arch 2020-05-18
    • 0

      In this workload we see latency spikes for catalog metadata operations on the config server into the ~20s range, and occasionally the operations timeout at 30s.

      Adjust the server parameters and/or test so that the latency for operations is < 1s.

      1. Turn off flow control to see if it has any effect, or
      2. Reduce the batch size in the workload to limit the per-operation latency on the config server, or
      3. Reduce the concurrency to limit the per-operation latency on the config server

      Or some combination.

            Assignee:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            lamont.nelson@mongodb.com Lamont Nelson
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: