-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
Drivers should remember greatest electionId seen, and disbelieve primaries with electionIds that aren't greater.
electionId (in isMaster response) will be backported to 2.6.x.
Justification: only one election per 30 secs, servers must have clocks synced within 30 sec and run 3.0+ (or the 2.6.x mongod with the backport) for read-your-writes consistency with w: "majority" and primary reads.
Set false primaries to state "Unknown", will be re-checked by next periodic monitoring
Justification: will step down and roll back soon, remains a primary with obsolete electionId until then
- depends on
-
CXX-597 Use electionId to detect stale primaries.
- Closed
-
CXX-598 Use electionId to detect stale primaries.
- Closed
-
PHPC-297 Use electionId to detect stale primaries.
- Closed
-
CDRIVER-636 Use electionId to detect stale primaries.
- Closed
-
NODE-455 Update SDAM specification support to cover electionId and Mongos load balancing.
- Closed
-
PYTHON-924 Use electionId to detect stale primaries.
- Closed
-
CSHARP-1274 Use electionId reported by ismaster to avoid sending operations to false primaries
- Closed
-
JAVA-1799 Use electionId reported by ismaster to avoid sending operations to false primaries
- Closed
-
RUBY-912 Use electionId to detect stale primaries.
- Closed
- is related to
-
SERVER-17975 Stale reads with WriteConcern Majority and ReadPreference Primary
- Closed
-
SERVER-19979 Detect replset clock skew from electionids
- Backlog
- related to
-
SERVER-21744 Clients may fail to discover new primaries when clock skew between nodes is greater than electionTimeout
- Closed