[GODRIVER-390] Getting a connection from a pool can be starved indefinitely Created: 27/Apr/18 Updated: 28/Oct/23 Resolved: 28/Apr/18 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | Connections |
| Affects Version/s: | 0.0.3 |
| Fix Version/s: | 0.0.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kristofer Brandow (Inactive) | Assignee: | Kristofer Brandow (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
In an application where the maximum number of connections has been dialed and they are all in use, attempting to get a new connection will wait, attempting to acquire a semaphore. If the application has further heavy load and the idle pool is never filled, no connections will be closed, which will indefinitely starve the attempt to get a new connection.
|
| Comments |
| Comment by Githook User [ 28/Apr/18 ] |
|
Author: {'email': 'kris@mongodb.com', 'username': 'skriptble', 'name': 'Kris Brandow'}Message: Fix race conditions and leaks in connection pool
Change-Id: I1390c184beb379d4cc775ba07b5d222342dc957e |
| Comment by Kristofer Brandow (Inactive) [ 27/Apr/18 ] |
|
Code Review: https://review.gerrithub.io/c/mongodb/mongo-go-driver/+/409354. |