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

Consider increasing the NETWORK component in Sharding suites to 3

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sharding

      In the fallout from SERVER-37913, esha.maharishi and I ruminated that it would help diagnose Sharding build failures if we increased the NETWORK component to verbosity 3. This would allow us to see what nodes are communicating when sending and receiving commands, allowing us to see for example which node in a config server returned a particular response.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            blake.oler@mongodb.com Blake Oler
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: