[GODRIVER-2918] Topology logicalSessionTimeoutMinutes may not be updated if server is removed Created: 24/Jul/23 Updated: 24/Jul/23 |
|
| Status: | Backlog |
| Project: | Go Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Kevin Albertson | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
Scope:
Background & MotivationSDAM describes behavior for tracking the topology-wide logicalSessionTimeoutMinutes:
The topology-wide logicalSessionTimeoutMinutes may not be updated if a server is removed from the topology description. Here is a failing test:
https://github.com/mongodb/mongo-go-driver/pull/1295/files#r1267070655 includes a suggested fix. The topology-wide logicalSessionTimeoutMinutes is calculated by checking each server's reported logicalSessionTimeoutMinutes. Each server reports logicalSessionTimeoutMinutes in the response the "hello". I expect this is low/no impact bug. The topology-wide logicalSessionTimeoutMinutes is used to determine session support. Sessions were introduced in server 3.6 (see DRIVERS-2337). Since the Go driver requires server 3.6 or newer, this may not have realistic impact. |