[SERVER-61715] Set a flag on the RecoveryUnit when it is not allowed to call abandonSnapshot() Created: 23/Nov/21 Updated: 27/Feb/23 Resolved: 27/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | techdebt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Sprint: | Execution Team 2022-02-07, Execution Team 2022-02-21, Execution Team 2022-03-07 | ||||||||
| Participants: | |||||||||
| Description |
|
Some operations require the snapshot not to change during execution. Like Lock-free reads. These operations should be able to set a flag to protect against incorrectness in any code sub-path unexpectedly calling abandonSnapshot() |
| Comments |
| Comment by Connie Chen [ 27/Feb/23 ] |
|
We should be able to create the RAII type without a new flag |