[CSHARP-3934] SDAM should give priority to electionId over setVersion when updating topology Created: 25/Oct/21  Updated: 05/Oct/22  Resolved: 05/Oct/22

Status: Closed
Project: C# Driver
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: PM Bot Assignee: Boris Dogadov
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates CSHARP-4298 SDAM should prioritize electionId ove... Closed
Issue split
split from DRIVERS-1954 SDAM should give priority to election... Closed
Server Compat: 4.4, 5.0, 5.1, 5.3
Quarter: FY23Q3
Upstream Changes Summary:

DRIVERS-1954:

  • Sync spec changes in 5bd06a8
  • Confirm tests fail with current updateRSFromPrimary implementation
  • Update updateRSFromPrimary to
    • Prioritize electionId before setVersion
    • Handle nullish values for both setVersion and electionId
    • always set maxElectionId and maxSetVersion together (they're a tuple value)
  • Confirm tests pass with changes
  • Update April 1 2022: Minor fixes were made, notably the spec files were using hello, where it should have been helloOk, see commit: 316c650 to pull in the latest.

 Description   

This ticket was split from DRIVERS-1954, please see that ticket for a detailed description.


Generated at Wed Feb 07 21:46:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.