-
Type:
Investigation
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
These were removed in 6.0 with NODE-5190, however it's unclear what the value of this removal was.
Let's keep the defaults that have been set but restore the ability to configure keepAliveInitialDelay (note that keepAlive should still not be toggleable)
Use Case
As a... driver user
I want... to be able to configure keepAliveInitialDelay
So that... I can choose a setting that works for my application
User Experience
- Use is able to set keepAliveInitialDelay to a value of their choice.
Dependencies
- N/A
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?
Acceptance Criteria
Implementation Requirements
- Ensure users can configure the keepAliveInitialDelay option via client (connection string and constructor), allow it to be a pass-through (no validation)
Testing Requirements
- Test the pass-through with valid and invalid values (negative numbers, non-numeric types)
Documentation Requirements
- API docs
- Add manual docs for the new option
Follow Up Requirements
- File ticket in V7 to change default keepAliveInitialDelay to 120s
- depends on
-
NODE-6245 Restore keepAliveInitialDelay configurability
-
- In Code Review
-