[SERVER-26415] Make sure to catch up to minValid before exiting rollback Created: 30/Sep/16 Updated: 20/Sep/17 Resolved: 03/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Judah Schvimer |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Sprint: | Repl 2016-11-21 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||
| Description |
|
Not doing so can (among other problems) result in an "Unrecoverable rollback error" if the node ever rolls back a second time. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 03/Nov/16 ] |
|
We wound up fixing the underlying issue in a slightly different way in |