Use Case

As a... Node Driver developer
I want... Node-specific keepAlive/delay fix to removed
So that... we don't have to keep a Node-specific fix in the driver

User Experience

• What is the desired/expected outcome for the user once this ticket is implemented?
• If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?

None

Dependencies

• upstream and/or downstream requirements and timelines to bear in mind

https://github.com/nodejs/node/pull/62004 is a fix for a Node bug that is present in Node20, 22, 24. It is now fixed in Node 25, and will be backported to 24 and 22, but probably not 20.
We added a Node driver fix for this bug, but once Node fixes this issue in the versions we support, we should remove this fix.

Risks/Unknowns

• What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
• Is there an opportunity for better cross-driver alignment or testing in this area?
• Is there an opportunity to improve existing documentation on this subject?

Node may re-introduce this bug.

Acceptance Criteria

Implementation Requirements

• functional reqs, potential snafus to avoid, performance targets, etc

Driver fix is removed, but the keepAlive/delay settings are properly configured on a socket.

Testing Requirements

• unit test, spec test sync, etc

New Drivers-level tests are passing, even after we remove this code. The new tests should be verifying that keepAlive/delay socket settings are being correctly set on the created sockets.

Documentation Requirements

• DOCSP ticket, API docs, etc

None

Follow Up Requirements

• additional tickets to file, required releases, etc
• if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward

None