[SERVER-32856] Roll Back to Checkpoint: fassert if we try to roll back when the consistency point is not majority committed Created: 23/Jan/18  Updated: 29/Jan/18  Resolved: 29/Jan/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Judah Schvimer
Resolution: Duplicate Votes: 0
Labels: rollback-functional
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-32196 Roll Back to Checkpoint: check suppor... Closed
Related
is related to SERVER-32588 Create flag to use rollback via refetch Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-02-12
Participants:

 Description   

We never want to use rollback via refetch with WT unless specifically instructed to with a server parameter. If we don't have a stable checkpoint (should only ever be right after initial sync), then we should fassert and instruct the user to do a resync.


Generated at Thu Feb 08 04:31:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.