[JAVA-4375] SDAM should give priority to electionId over setVersion when updating topology - MongoDB Jira

XML

Word

Printable

JSON

Server Compat:
- 4.4
- 5.0
- 5.1
- 5.3
Quarter:
- FY23Q3
Upstream Changes Summary:
Hide

~~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.
Show
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.

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

See ~~JAVA-4550~~ for a patch that must be applied to the one that was reverted here.

duplicates

JAVA-4707 Prioritize electionId over setVersion on 6.0+ servers

is related to

JAVA-4550 Excessive logging of maxElectionId and maxSetVersion

JAVA-4535 Driver should reconnect to replica set restarted as 'fresh'

split from

DRIVERS-1954 SDAM should give priority to electionId over setVersion when updating topology