[GODRIVER-2423] WaitQueueTimeoutError reports pinned connections when no pinning occurs Created: 16/May/22 Updated: 08/Nov/23 Resolved: 29/Aug/23 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.12.2 |
| Type: | Bug | Priority: | Unknown |
| Reporter: | Kevin Albertson | Assignee: | Qingyang Hu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Quarter: | FY24Q3 | ||||
| Documentation Changes: | Not Needed | ||||
| Documentation Changes Summary: | 1. What would you like to communicate to the user about this feature? |
||||
| Description |
|
Scope
Background & Motivation When connected to a Load Balancers, drivers are required to pin connections to cursors and transactions. The Go driver always reports pinned connections in WaitQueueTimeoutError, even if no connection pinning occurs. That can cause confusing error messages when not connected to a load balanced cluster. Example:
|
| Comments |
| Comment by Githook User [ 08/Nov/23 ] | ||||||
|
Author: {'name': 'Qingyang Hu', 'email': '103950869+qingyang-hu@users.noreply.github.com', 'username': 'qingyang-hu'}Message: | ||||||
| Comment by Githook User [ 29/Aug/23 ] | ||||||
|
Author: {'name': 'Qingyang Hu', 'email': '103950869+qingyang-hu@users.noreply.github.com', 'username': 'qingyang-hu'}Message: | ||||||
| Comment by Matt Dale [ 03/Aug/23 ] | ||||||
|
Ways this error could be better:
Ways to improve pinned cursors info:
I think #1 is probably good enough and simpler, but either works. |