[SERVER-33590] Add targeted rollback test for rollback recoverability Created: 01/Mar/18 Updated: 06/Dec/22 Resolved: 29/May/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: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | rollback-optional | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Participants: | |||||||||
| Description |
|
double_rollback.js and double_rollback_early.js test that rollback via refetch does not corrupt data due to double rollback scenarios. It would be good to make an analogous test for rollback to a stable timestamp to show that it is in fact recoverable. This would do a double rollback and show that no "minValid" is required post rollback to do another rollback. |
| Comments |
| Comment by Judah Schvimer [ 29/Mar/18 ] |
|
We're marking this as optional since jepsen should give us coverage, albeit less reproducibly. |