-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.1.2
-
Component/s: Storage
-
None
-
ALL
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
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.