[SERVER-6312] ensure fassert for assertions occurring after db writes Created: 05/Jul/12 Updated: 17/Mar/17 Resolved: 17/Mar/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 2.1.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Andy Schwerin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
If code should happen to hit a uassert, massert, or anything that throws an exception, after performing database writes to memory, we should ensure that the database aborts (or somehow undo the writes already done). Otherwise, data corruption might be left behind. |
| Comments |
| Comment by Andy Schwerin [ 17/Mar/17 ] |
|
This happened as a result of the storage engine api refactoring for the 3.0 release. |