Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.5.8
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2017-03-27, Repl 2017-04-17, Repl 2017-05-08, Repl 2017-05-29
Linked BF Score:
0

ReplicationCoordinatorImpl::_slaveInfo and TopologyCoordinatorImpl::_hbdata contain a lot of duplicate information, and keeping that state separate prevents certain events from being triggered when information comes in via heartbeats or via replSetUpdatePosition. We should push all this information down into the TopologyCoordinator and use it as the single source of information for making decisions about secondary state and replication progress.

is depended on by

SERVER-29076 Replace all usage of heartbeat op times with lastAppliedOpTime / lastDurableOptime

Backlog

SERVER-29077 Rename memberHeartbeatData in topology coordinator

Closed

SERVER-29078 Eliminate use of memberHeartbeatData in replication_coordinator_impl

Closed

is duplicated by

SERVER-29097 Nodes should update liveness info when they receive a heartbeat response without newer optimes

Closed

is related to

SERVER-26746 Nodes should update their own term from the term in heartbeats

Closed

SERVER-34728 Heartbeats are used to advance replication commit point

Closed

SERVER-20886 ensure all uses of rsConfig indexes confirm they are from a matching config version before use

Closed

(2 is related to)

Assignee:: Unassigned

Reporter:: Spencer Brody (Inactive)

Participants:: Githook User, Spencer Brody

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: Nov 10 2016 11:15:13 PM UTC

Updated:: Apr 27 2018 08:22:10 PM UTC

Resolved:: May 16 2017 05:10:20 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates