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

prioritize sharding metadata traffic in workload scheduling like we do for replication traffic

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • 200

      We exclude replication traffic (like heartbeats and oplog queries) from taking tickets in execution control and admission control. Sharding metadata traffic should do the same.

            Assignee:
            Unassigned Unassigned
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: