Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
Fully Compatible
-
ALL
-
v4.4
-
Repl 2020-05-18
-
37
Description
When heartbeat response has a newer config, the node tries to install the config immediately without updating the heartbeat state. SERVER-47949 doesn't allow a new config during catchup mode, but catchup mode relies on the latest heartbeat state. Thus the primary will never exit catchup mode if it sees a newer config in heartbeat responses.
We should update the heartbeat state even if topology coordinator sees a newer config.
It's less ideal to move the logic of SERVER-47949 to topology coordinator where it decides to install the new config because some of the information is only available in replication coordinator, like whether the node can accept writes.
Attachments
Issue Links
- is depended on by
-
SERVER-47949 Do not install higher safe config via heartbeats in primary
-
- Closed
-
- is related to
-
SERVER-48178 Finding self in reconfig may be interrupted by closing connections due to rollback
-
- Closed
-
-
SERVER-48179 Removing rollback node will crash the node on transition out of rollback
-
- Closed
-