-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v4.4
-
Repl 2020-09-07, Repl 2020-09-21, Repl 2020-10-05, Repl 2020-10-19, Repl 2020-11-02, Repl 2020-11-16
-
19
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
After SERVER-29030, we cancel our own heartbeat requests if we receive a heartbeat request that announces a new primary. Since we don't update our knowledge of the primary when we receive a heartbeat request, it seems possible to continuously schedule and cancel our heartbeat requests. As a result, a node in initial sync may not be able to find a sync source, because it has not successfully received 2N heartbeats from other nodes, and eventually the node will shut down.
- causes
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
-
SERVER-48793 Remove "targetIndex" from ReplicationCoordinatorImpl::_handleHeartbeatResponse()
-
- Closed
-
- is related to
-
SERVER-29030 Announce new primary via heartbeat requests
-
- Closed
-