[DRIVERS-2421] Drivers should include topology description in server selection timeout errors Created: 19/Aug/22 Updated: 21/Aug/23 |
|
| Status: | Implementing |
| Project: | Drivers |
| Component/s: | Server Selection |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaitlin Mahar | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Changes: | Needed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Quarter: | FY24Q2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Downstream Changes Summary: | NA |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Start date: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
SummaryDrivers that do not already include the topology description in server selection timeout error messages should do so. Some drivers do this already, e.g. Python (see MotivationWho is the affected end user?Users who are encountering server selection timeout errors. How does this affect the end user?Currently it can be hard for them or us to tell what the driver's view of their topology is, making it hard to diagnose why server selection is failing. How likely is it that this problem or use case will occur?This is likely to impact anyone who is encountering server selection timeout errors, which are fairly common. Users often encounter these while trying to connect to a new cluster, write a new application, when their cluster gets in an unhealthy state, etc. If the problem does occur, what are the consequences and how severe are they?The user has difficulty debugging and fixing the problem. Is this issue urgent?No. Is this ticket required by a downstream team?No, but it would help users of downstream tools like mongosh if the Node driver doesn't include this information already. Is this ticket only for tests?No, functional changes are needed. |