[SERVER-53720] Tag onCommit/onRollback Changes with unique identifiers to log in case they throw when later run Created: 12/Jan/21 Updated: 06/Dec/22 Resolved: 14/Jan/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
If some Change fails in the RecoveryUnit::commitRegisteredChanges() or abortRegisteredChanges functions, we have the error message, but we have no trace of where the code for the Change is: it won't be in a stack trace. It would help diagnose issues more quickly if we could immediately identify where in the code to find the Change definition. |