Implement ConnectionPoolStats in gRPC AsyncClientFactory

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Networking & Observability
    • Fully Compatible
    • ALL
    • Egress gRPC 2025-02-14
    • 2
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Implement the ConnectionPoolStats in the AsyncClientFactory & expose them through appendStats, setting any stats (like refreshing) to 0 if they are not relevant. We will want to write a test similar to jstests/with_mongot/mongotmock/configure_mongot_connpool.js in order to test these stats, though it can be more straightforward as we don't care about refreshing stats or connection maximums, as our gRPC implementation uses one connection per remote anyways.

              Assignee:
              Joseph Prince
              Reporter:
              Erin McNulty
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: