[DRIVERS-2482] Reduce serverSelectionTimeoutMS default value Created: 25/Oct/22 Updated: 18/Oct/23 |
|
| Status: | Backlog |
| Project: | Drivers |
| Component/s: | Server Selection |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Alex Bevilacqua | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | FY24Q2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Changes: | Needed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
The default serverSelectionTimeoutMS of 30000 may be too long a default that negatively impacts application resilience. In general 30 seconds is too long as the server is likely unavailable and unlikely to recover within the 30 seconds. Additionally 30 seconds may match other service timeouts (ex: Heroku's Request Timeout) which when overlapped can result in user-facing errors. Lowering the default to something like 15000 would ensure it remains above the heartbeatFrequencyMS default of 10000 and may improve application resilience by allowing faster server selection. Note this proposed change would only impact the default value of serverSelectionTimeoutMS, which can still be configured by users as needed. There should also be no impact to Client Side Operations Timeout as serverSelectionTimeoutMS is not being deprecated. |
| Comments |
| Comment by Shane Harvey [ 18/Oct/23 ] |
|
Linking DRIVERS-1262 since that project would expand the scope of serverSelectionTimeoutMS. |
| Comment by Tom Selander [ 25/Oct/22 ] |
|
Leads Triage: Good with this, should be small spec change and some tests around the URI.
Might be a good quick win for FY23Q4? |