Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
Fully Compatible
-
ALL
-
Repl 2020-06-15
-
18
Description
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.
Attachments
Issue Links
- 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
-