-
Type: Improvement
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
None
-
Storage Execution
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.
- related to
-
SERVER-53415 Intent Lock timeout lead to server crash
- Closed