[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: |
|
||||||||||||||||
| 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. |