-
Type: Epic
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Done
-
Connection pool improvements
-
5
-
12
-
12
-
150
-
Summary
Address unnecessary connection pool clears and connection churn on operations with a small context timeout.
Motivation
Who is the affected end user?
Customers and users setting small context timeouts on operations.
How does this affect the end user?
The Go driver can enter a state where all connections in a connection pool are perished (usually caused by a connection pool clear due to encountering a timeout during new connection establishment) and almost no new connections can be established in-line with an operation due to the low operation timeout. Customers using the Go driver may encounter application outages as a result of the Go driver’s inability to recover from this state.
How likely is it that this problem or use case will occur?
There are known customers experiencing this issue. It is likely if users are setting a small context timeout in operations.
If the problem does occur, what are the consequences and how severe are they?
A problem can result in an outage.
Is this issue urgent?
Yes, there are known customers that cannot migrate workloads to the Go driver due to this issue.
Is this ticket required by a downstream team?
No
Is this ticket only for tests?
No
Cast of Characters
Engineering Lead: Matt Dale
Document Author: Matt Dale
POCers:
Product Owner:
Program Manager:
Stakeholders: