Loading...

XML

Word

Printable

JSON

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

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

v4.4
Sprint:
Repl 2020-10-19, Repl 2020-11-16, Repl 2020-11-30, Repl 2020-12-14, Repl 2020-12-28, Repl 2021-03-08, Repl 2021-03-22
Linked BF Score:
49
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

At the end of rollback, the node transitions to secondary, assuming the state is still in ROLLBACK. However a reconfig via heartbeat may have changed it to REMOVED.

is related to

SERVER-48178 Finding self in reconfig may be interrupted by closing connections due to rollback

Closed

related to

SERVER-48102 Update heartbeat state on primary even if heartbeat response includes a new config

Closed

SERVER-49388 Complete TODO listed in SERVER-48178

Closed

Assignee:: Wenbin Zhu
Reporter:: Siyuan Zhou
Participants:: Githook User, Siyuan Zhou, Tess Avitabile, Wenbin Zhu
Votes:: 0 Vote for this issue
Watchers:: 10 Start watching this issue

Created:: May 13 2020 07:36:52 AM UTC
Updated:: Oct 29 2023 10:08:16 PM UTC
Resolved:: Mar 17 2021 12:12:39 AM UTC
Confidence Status Last Update:: 11/Mar/21 7:03 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates