While working on DRIVERS-2711 POC (NODE-5723), on fixing a bug in the unified test runner, it was discovered that the Node driver awaits(or reports that it awaits) the first server heartbeat regardless of the configured value of the serverMonitoringMode option, which leads to failures on the following spec tests:

• connect with serverMonitoringMode=auth >= 4.4
• connect with serverMonitoringMode=stream >= 4.4

Note that the failure is only on the assertion for the awaited field of the first ServerHeartbeatSucceededEvent.

Use Case

As a... driver engineer
I want... to change our heartbeat succeeded emit logic to not await the first heartbeat
So that... our SDAM behaviour is spec-compliant

User Impact

• Minor, likely not noticed by users

Dependencies

• None

Unknowns

• Is the heartbeat actually awaited or does the driver only report that it is awaited?

Acceptance Criteria

Implementation Requirements

• Ensure that the first heartbeat emitted when connecting to a server is never await regardless of the value of serverMonitoringMode when connecting to servers that have streamable heartbeats (mongo versions >= 4.4)

Testing Requirements

• Unskip tests skipped in when working on DRIVERS-2875 implementation (NODE-6052)

Documentation Requirements

• None

Follow Up Requirements

• None