Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.1.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Replication
Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2024-06-10
Linked BF Score:
0
Story Points:
2
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

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

Closed

related to

SERVER-90854 Remove the obsolete DropPendingCollectionReaper

Closed

SERVER-86266 remove MMAPv1 logic from RollbackViaRefetch code

Closed

Assignee:: Kishore Devireddy
Reporter:: Jiawei Yang
Participants:: Githook User, Jiawei Yang, Kishore Devireddy
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jan 11 2024 09:20:24 PM UTC
Updated:: Dec 02 2024 06:16:21 PM UTC
Resolved:: Jun 06 2024 03:35:05 AM UTC
Confidence Status Last Update:: 04/Jun/24 1:00 AM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates