Make connection pool and connection state observable

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Done
    • Priority: Major - P3
    • 3.5.0
    • Affects Version/s: None
    • Component/s: API, Monitoring
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      It'd be potentially useful for the status of a replica set connection to be observable, so an observer can subscribe and be made aware of any events (eg. change in primary, no primary or no majority, etc.).

      Similarly, it could be useful for the status of the connection pool and of each connection to be observable.

      Specifically, the driver should surface the following events to listeners:

      1. connection pool opened
      2. connection pool closed
      3. connection added to pool
      4. connection removed from pool
      5. connection checked out of pool
      6. connection checked in to pool
      7. connection pool wait queue entered
      8. connection pool wait queue exited
      9. connection opened
      10. connection closed

              Assignee:
              Ross Lawley
              Reporter:
              Jeffrey Yemin
              None
              Votes:
              7 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: