[GODRIVER-2524] SDAM should prioritize electionId over setVersion only on >=6.0 servers Created: 15/Aug/22  Updated: 28/Oct/23  Resolved: 20/Oct/22

Status: Closed
Project: Go Driver
Component/s: SDAM
Affects Version/s: None
Fix Version/s: 1.11.0

Type: Improvement Priority: Unknown
Reporter: PM Bot Assignee: Preston Vasquez
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on GODRIVER-2207 SDAM should give priority to election... Closed
Duplicate
is duplicated by GODRIVER-2207 SDAM should give priority to election... Closed
Issue split
split from DRIVERS-2412 SDAM should prioritize electionId ove... Implementing
Related
is related to GODRIVER-2207 SDAM should give priority to election... Closed
Quarter: FY23Q3
Upstream Changes Summary:

DRIVERS-2412:

  • Sync spec changes in 37c32c
  • Confirm tests fail with current updateRSFromPrimary implementation
  • Summary of updateRSFromPrimary changes:
    • If maxWireVersion 17 or greater
    • Prioritize electionId before setVersion
    • Handle nullish values for both setVersion and electionId
    • always set maxElectionId and maxSetVersion together (they are a tuple value)
  • Confirm tests pass with changes

Join #drivers-2412-sdam-should-prioritize-electionid-over-setversion on slack for any questions

Backwards Compatibility: Fully Compatible

 Description   

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



 Comments   
Comment by Githook User [ 18/Oct/22 ]

Author:

{'name': 'Preston Vasquez', 'email': '24281431+prestonvasquez@users.noreply.github.com', 'username': 'prestonvasquez'}

Message: GODRIVER-2524 SDAM should prioritize electionId over setVersion only on >=6.0 servers (#1090)
Branch: master
https://github.com/mongodb/mongo-go-driver/commit/acfd7a3e1a45095601eca2399cb40f2372a730ca

Generated at Thu Feb 08 08:38:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.