In DRIVERS-1954, we discovered that the electionId/setVersion change could not be implemented or else drivers would break when replica set restore is run using a pre 6.0 compatible version of Ops Manager.
Instead of waiting until until these old versions of Ops Manager are EOL, I propose we only implement the new electionId/setVersion comparison logic on >=6.0 servers. This will avoid the regression assuming that old Ops Manager versions do not support backup/restore >=6.0 servers.
Using this approach we can fix the original bug in DRIVERS-1954 on >=6.0 servers. Drivers will still be vulnerable to the bug on <6.0 servers but that's okay because we're already in that position now.
- is duplicated by
-
DRIVERS-1954 SDAM should give priority to electionId over setVersion when updating topology
- Closed
- related to
-
DRIVERS-1954 SDAM should give priority to electionId over setVersion when updating topology
- Closed
- split to
-
RUST-1446 SDAM should prioritize electionId over setVersion only on >=6.0 servers
- Backlog
-
CXX-2566 SDAM should prioritize electionId over setVersion only on >=6.0 servers
- Blocked
-
CDRIVER-4455 SDAM should prioritize electionId over setVersion only on >=6.0 servers
- Closed
-
CSHARP-4298 SDAM should prioritize electionId over setVersion only on >=6.0 servers
- Closed
-
GODRIVER-2524 SDAM should prioritize electionId over setVersion only on >=6.0 servers
- Closed
-
JAVA-4707 Prioritize electionId over setVersion on 6.0+ servers
- Closed
-
MOTOR-1018 SDAM should prioritize electionId over setVersion only on >=6.0 servers
- Closed
-
NODE-4546 SDAM should prioritize electionId over setVersion only on >=6.0 servers
- Closed
-
PHPC-2145 SDAM should prioritize electionId over setVersion only on >=6.0 servers
- Closed
-
PYTHON-3400 SDAM should prioritize electionId over setVersion only on >=6.0 servers
- Closed
-
RUBY-3090 SDAM should prioritize electionId over setVersion only on >=6.0 servers
- Closed
- mentioned in
-
Page Loading...