[GODRIVER-2829] Requesting an immediate heartbeat check after an error doesn't work for streaming heartbeats Created: 03/May/23 Updated: 18/Jan/24 |
|
| Status: | Backlog |
| Project: | Go Driver |
| Component/s: | SDAM |
| Affects Version/s: | 1.10.3, 1.11.4 |
| Fix Version/s: | 2.1.0 |
| Type: | Bug | Priority: | Unknown |
| Reporter: | Matt Dale | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
There are a few places that the Go driver attempts to request an immediate server heartbeat check while processing an error:
That command is supposed to stop the currently running check and immediately request a new one (see here). However, calling RequestImmediateCheck doesn't cancel the current check and waitUntilNextCheck function is only run if the currently running check is cancelled, so RequestImmediateCheck basically does nothing most of the time. |