[CDRIVER-4057] Reset setName when stale primary detected Created: 06/Jul/21 Updated: 15/Apr/22 |
|
| Status: | Backlog |
| Project: | C Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | 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 | ||
| Epic Link: | CDRIVER-4107 |
| Description |
|
Motivation Several SDAM specification tests make assertions that the setName on a server description is unset if it is a stale primary is reset to the state Unknown. The test runner currently does not assert anything about the setName if it is null in the outcome. In attempting to add the check as part of
I suspect the correct behavior, as the test asserts, is to reset the setName when a stale primary is detected. I think this is low impact currently. I do not think this interferes with SDAM correctness. But it may be an inconsistency with other drivers. Users may incorrectly see a set setName in a ServerChangedEvent. Scope |