[GODRIVER-1902] pool.Put() always releases the semaphore Created: 26/Feb/21 Updated: 01/Mar/22 Resolved: 01/Mar/22 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | Connections |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Isabella Siu (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | new-eng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
topology.pool always releases the semaphore, even if the connection being put back is nil or from a different pool, so more connections can be available than there really are. |
| Comments |
| Comment by Matt Dale [ 01/Mar/22 ] |
|
The pool no longer uses a semaphore to manage max connections (as of |