Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.4.1, 4.7.0
Affects Version/s: None
Component/s: None
Labels:
- safe-reconfig-related

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v4.4
Sprint:
Security 2020-06-29, Security 2020-07-13
Linked BF Score:
14
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: Mark Benvenuto
Reporter:: Siyuan Zhou
Participants:: Githook User, Judah Schvimer, Mark Benvenuto, Pavithra Vetriselvan, Siyuan Zhou, Spencer Jackson
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: May 13 2020 07:23:04 AM UTC
Updated:: Oct 29 2023 10:08:16 PM UTC
Resolved:: Jul 08 2020 11:24:05 PM UTC
Confidence Status Last Update:: 17/Jun/20 7:41 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates