Make load_balanced_server_status_metrics.js use a unique port within the test's port range

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Service Arch
    • Fully Compatible
    • ALL
    • Service Arch 2024-03-04
    • 109
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In BF-31900, we see mongod/s startup fail because the port 22064 is already in use by the load_balanced_server_status_metrics.js test, which hardcodes in the use of the port.

      We should change this test, along with proxy_protocol_connect.js, to use unique ports within their allocated ranges.

            Assignee:
            Erin McNulty
            Reporter:
            Erin McNulty
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: