[GODRIVER-3021] Document connection pool timeout causes Created: 20/Oct/23  Updated: 30/Oct/23

Status: Backlog
Project: Go Driver
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Unknown
Reporter: Preston Vasquez Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to GODRIVER-2669 Getting a connection from the pool is... Closed

 Description   

The Go Driver often gets troubleshooting tickets for errors encountered when checking out a connection pool, see here. We should extend "docs/common-issues.md" to include a section addressing these errors and common causes. The following is a non-exhaustive list of possible issues:

1. Operation timeout
2. Setting a max pool size less than the number of pending operations
3. Canceling the context asynchronously before the operations complete
4. Executing with CSOT
5. Executing with a deadline / timeout on the operation context

Here is a gist of issues that can occur from canceling / timing out: https://gist.github.com/prestonvasquez/1e9137e4ed85733967cb8758cd8e0fe3

Other solutions would be to check the packets being sent over the wire either using event monitoring or a packet analyzer such as wire shark.


Generated at Thu Feb 08 08:39:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.