-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Fully Compatible
-
Repl 2024-06-10
-
0
-
2
There is still a forceRollbackViaRefetch parameter to force rollback-via-refetch, so should we still remove that method or we remove that parameter together.
- duplicates
-
SERVER-47022 Oplog application mode must be set to kRecovering when applying oplog entries after rollbackViaRefetch
- Closed
-
SERVER-48603 Rollback via refetch can result in out of order timestamps
- Closed
- is related to
-
SERVER-97775 Write rolled back oplog entry to rollback file for debugging
- Open
- related to
-
SERVER-90854 Remove the obsolete DropPendingCollectionReaper
- Closed
-
SERVER-86266 remove MMAPv1 logic from RollbackViaRefetch code
- Closed