[SERVER-38261] Execute rollback changes on BiggieSE's recovery unit destructor and disallow nested changes Created: 27/Nov/18 Updated: 29/Oct/23 Resolved: 29/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Storage NYC 2018-12-03 |
| Participants: |
| Description |
|
Today, nested changes are allowed in Biggie's recovery unit, we should avoid this complexity and execute rollback changes when the recovery unit is destructed. Right now the rollback changes are only executed when calling abortUnitOfWork() explicitly. |
| Comments |
| Comment by Githook User [ 29/Nov/18 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |