[SERVER-26990] Unify tracking of secondary state between replication and topology coordinators Created: 10/Nov/16  Updated: 27/Apr/18  Resolved: 16/May/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.5.8

Type: Improvement Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-29076 Replace all usage of heartbeat op tim... Backlog
is depended on by SERVER-29077 Rename memberHeartbeatData in topolog... Closed
is depended on by SERVER-29078 Eliminate use of memberHeartbeatData ... Closed
Duplicate
is duplicated by SERVER-29097 Nodes should update liveness info whe... Closed
Related
is related to SERVER-26746 Nodes should update their own term fr... Closed
is related to SERVER-34728 Heartbeats are used to advance replic... Closed
is related to SERVER-20886 ensure all uses of rsConfig indexes c... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2017-03-27, Repl 2017-04-17, Repl 2017-05-08, Repl 2017-05-29
Participants:
Linked BF Score: 0

 Description   

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.



 Comments   
Comment by Githook User [ 15/May/17 ]

Author:

{u'username': u'mtrussotto', u'name': u'Matthew Russotto', u'email': u'matthew.russotto@10gen.com'}

Message: SERVER-26990 Unify tracking of secondary state between replication and topology coordinators

This fixes a bug in the 6adc71f6cf069803f9c1288aef88ffe0d21c6ffe which caused crashes when a
sync source change was requested of a node not in the configuration. It also fixes a dependency
problem affecting the shared library build.
Branch: master
https://github.com/mongodb/mongo/commit/c88c4809c2440d286ed0fc29e1e8d684f015e563

Comment by Githook User [ 04/May/17 ]

Author:

{u'username': u'mtrussotto', u'name': u'Matthew Russotto', u'email': u'matthew.russotto@10gen.com'}

Message: Revert "SERVER-26990 Unify tracking of secondary state between replication and topology coordinators"

This reverts commit 6adc71f6cf069803f9c1288aef88ffe0d21c6ffe.
Branch: master
https://github.com/mongodb/mongo/commit/b2d70219b85a3462fb902618500b2f63f5f188b5

Comment by Githook User [ 04/May/17 ]

Author:

{u'username': u'mtrussotto', u'name': u'Matthew Russotto', u'email': u'matthew.russotto@10gen.com'}

Message: SERVER-26990 Unify tracking of secondary state between replication and topology coordinators

This removes the slaveInfo structure and consolidates secondary state into the topology coordinator
memberHeartbeatData.
Branch: master
https://github.com/mongodb/mongo/commit/6adc71f6cf069803f9c1288aef88ffe0d21c6ffe

Comment by Spencer Brody (Inactive) [ 11/Nov/16 ]

Investigate SERVER-20886 as part of this and determine if there's any more work to be done on that ticket

Generated at Thu Feb 08 04:13:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.