Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.4.0
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Repl 2020-06-15
Linked BF Score:
18
Confidence Status:
None
Work Order:
3

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

That would probably cause the initial sync attempt to fail eventually, but it might be worth writing something that checks for REMOVED state proactively and helps us fail quickly and gracefully.

is related to

SERVER-35649 Nodes removed due to isSelf failure should re-attempt to find themselves

Closed

split to

SERVER-48530 Relax invariant around timestamping for nodes in REMOVED

Closed

Assignee:: Matthew Russotto
Reporter:: Vesselina Ratcheva (Inactive)
Participants:: Daniel Gottlieb, Githook User, Judah Schvimer, Matthew Russotto, Vesselina Ratcheva
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: May 28 2020 08:53:16 PM UTC
Updated:: Oct 29 2023 10:07:39 PM UTC
Resolved:: Jun 10 2020 05:32:02 PM UTC
Confidence Status Last Update:: 02/Jun/20 5:54 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates