[GODRIVER-3107] Connection leak in runHellos() in rtt_monitor Created: 26/Jan/24 Updated: 29/Jan/24 |
|
| Status: | Investigating |
| Project: | Go Driver |
| Component/s: | Connections |
| Affects Version/s: | 1.13.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Unknown |
| Reporter: | Klemen Košir | Assignee: | Matt Dale |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Go Drivers
|
| Description |
Detailed steps to reproduce the problem?Connecting a simple Go client to a replica set cluster and the disconnecting it leaves behind RTTMonitor connections that keep sending commands to each Mongo host. See README in https://github.com/KarboniteKream/mongo-go-rtt-monitor-leak Definition of done: what must be done to consider the task complete?Disconnecting a client no longer leaves behind goroutines with runHellos sending commands to Mongo nodes. The exact Go version used, with patch level:$ go version The exact version of the Go driver used:$ go list -m go.mongodb.org/mongo-driver Describe how MongoDB is set up. Local vs Hosted, version, topology, load balanced, etc.Hosted (private cloud) replica set with 3 members, running MongoDB 4.4.17. The operating system and version (e.g. Windows 7, OSX 10.8, ...)Client running on macOS 14.2.1 and various Linux flavors (CentOS, Alpine). Security VulnerabilitiesIf you've identified a security vulnerability in a driver or any other MongoDB project, please report it according to the instructions here |
| Comments |
| Comment by PM Bot [ 26/Jan/24 ] |
|
Hi klemen.kosir@kream.io, thank you for reporting this issue! The team will look into it and get back to you soon. |