[JAVA-4707] Prioritize electionId over setVersion on 6.0+ servers Created: 15/Aug/22  Updated: 28/Oct/23  Resolved: 13/Oct/22

Status: Closed
Project: Java Driver
Component/s: SDAM
Affects Version/s: None
Fix Version/s: 4.8.0

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

Issue Links:
Duplicate
is duplicated by JAVA-4375 SDAM should give priority to election... Closed
Issue split
split from DRIVERS-2412 SDAM should prioritize electionId ove... Implementing
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
Documentation Changes: Not Needed

 Description   

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



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

Author:

{'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}

Message: Prioritize electionId over setVersion on 6.0+ servers (#1010)

JAVA-4707
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/fef2873eaf792e93c1f600ca16a90519c9410227

Generated at Thu Feb 08 09:02:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.