[SERVER-18280] ReplicaSetMonitor should use electionId to avoid talking to old primaries - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 2.6.11, 3.0.5, 3.1.4
Component/s: Internal Client, Replication
Labels:
None

Backwards Compatibility:
Minor Change
Backport Completed:

2.6.11, 3.0.5
Sprint:
Sharding 4 06/05/15

Description

To get "sticky read your writes" behavior out of the internal replica set client, used by mongos and the shell, the internal client's code for replica set monitoring and server selection should accept as "primary" nodes reporting a larger electionId value than the most recently selected primary node.

Note that in 2.6 and 3.0, large clock skews (> 30 seconds) between the replica set member nodes may lead to clients that observe an election being unable to issue writes or primary reads. The solution would be to restart those clients.

Attachments

Issue Links

is depended on by

CXX-597 Use electionId to detect stale primaries.

Closed

is documented by

DOCS-5326 consistency/isolation/recency tracking ticket

Closed

is related to

SERVER-19978 Log electionid

Backlog

SERVER-19979 Detect replset clock skew from electionids

Backlog

Activity

People

Assignee:: Daniel Alabi

Reporter:: Andy Schwerin

Participants:: A. Jesse Jiryu Davis, Andy Schwerin, Daniel Alabi, Githook User

Votes:: 0 Vote for this issue

Watchers:: 10 Start watching this issue

Dates

Created:: Apr 30 2015 08:00:11 PM UTC

Updated:: Jul 14 2017 07:24:12 PM UTC

Resolved:: Jun 02 2015 01:34:49 PM UTC