-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Replication
-
ALL
-
30
In order to reach a consistent state after doing a rollbackViaRefetch, the rollback node sets its own minValid to the top of sync source's oplog at the start of recovery. It therefore must be able to replicate and apply up to that lastApplied to complete the recovery. However, if at some point mid-recovery the necessary oplog entries are no longer in the set (either due to a rollback or an unclean shutdown), the rollback node will end up in an unrecoverable state as it may only choose a sync source that has them.
- related to
-
SERVER-43867 Work around unrecoverability of rollback via refetch in tests
- Closed
-
SERVER-38925 Rollback via refetch can cause _id duplication when enableMajorityReadConcern:false
- Closed