[SERVER-29520] Ensure that any failure during oplog application as part of recovery results in an fassert Created: 08/Jun/17 Updated: 27/Oct/23 Resolved: 26/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Judah Schvimer |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | neweng, rollback-optional | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Repl 2018-01-15 |
| Participants: |
| Description |
|
We currently fassert if SyncTail::syncApply returns a bad status during startup recovery. But SyncTail::syncApply can uassert in various cases. We should wrap that call in a try-catch and fassert on failure. |
| Comments |
| Comment by Judah Schvimer [ 26/Feb/18 ] |
|
Completed in https://github.com/mongodb/mongo/commit/f2b0ffdc54647aa6dd7cddfb740a63f419d30d55 as part of |