Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-5230

ConnectionPoolClearedEvent is emitted after ConnectionClosed and ConnectionCheckoutFailed events on network error

    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      Use Case

      As a Node Driver Engineer
      I want ConnectionPoolCleared events to be emitted before a Connection fails to be checked out as a result of a network error.
      So that our CMAP implementation is spec compliant once DRIVERS-1003 merges.

      User Impact

      • Unknown

      Unknowns

      • How do we guarantee the correct ordering of these events?
      • Would this affect end users?

      Acceptance Criteria

      Implementation Requirements

      • Ensure that when a network error occurs on Connection checkout that the ConnectionPoolCleared event gets emitted before the ConnectionClosed and ConnectionCheckOutFailed events.

      Testing Requirements

      • Unskip logging spec test from NODE-4720
      • Remove test/connection-monitoring-and-pooling/unified-cmap-node-specs/connection-logging.json
      • Remove code to run modified spec test in test/integration/connection-monitoring-and-pooling/connection_monitoring_and_pooling.test.ts

      Documentation Requirements

      • None

            Assignee:
            Unassigned Unassigned
            Reporter:
            warren.james@mongodb.com Warren James
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: