-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
ALL
-
v4.4
-
Security 2020-06-29, Security 2020-07-13
-
14
When a node installs a new config, it needs to create a new connection to find itself in the config. If the node start to roll back, the connection will be closed. Thus the node thinks it's not in this config and will transition to REMOVED. This issue becomes worse when authentication is enabled since more network roundtrips are involved.
- related to
-
SERVER-48102 Update heartbeat state on primary even if heartbeat response includes a new config
- Closed
-
SERVER-48179 Removing rollback node will crash the node on transition out of rollback
- Closed
-
SERVER-35649 Nodes removed due to isSelf failure should re-attempt to find themselves
- Closed
-
SERVER-49388 Complete TODO listed in SERVER-48178
- Closed
-
SERVER-49305 Remove reconfig retries in our tests
- Closed