Add check for large connection counts after tests

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Networking & Observability
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In BF-40359, we saw an issue where config server connection pools would create unbounded numbers of connections due to bugs in the RSM/ConnectionPool, but this was only caught because the system happened to run out of ports. We should have automatic checks for connection counts after tests run to ensure this kind of thing can be caught.

      This could implemented via hook or possibly by setting aggressive values for maxConnections.

            Assignee:
            Unassigned
            Reporter:
            Patrick Freed
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: