-
Type: Bug
-
Resolution: Duplicate
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
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
- duplicates
-
NODE-6469 Add test that PoolClearedEvent is emitted before ConnectionCheckedInEvent/ConnectionCheckOutFailedEvent
- Closed
- has to be done before
-
NODE-4766 CMAP connection establishment failure tests
- Blocked
- is fixed by
-
NODE-6469 Add test that PoolClearedEvent is emitted before ConnectionCheckedInEvent/ConnectionCheckOutFailedEvent
- Closed
- related to
-
NODE-4720 Add log messages to CMAP spec
- Closed