When recording errors, WT can return an error message back to the mongod layer. Right now when WT returns an error like WT_ROLLBACK due to hitting a write conflict, it often returns a generic message "conflict between concurrent operations". Unfortunately, that often isn't enough during unexpected situations to understand the details of what went wrong. It would be helpful if WT included more detailed information like which transactions conflicted, was the conflict generated on a prepared update, and what timestamps were the writes at.
- is related to
-
WT-15299 Precise checkpoint data mismatch
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
WT-15165 Design a data structure to temporarily store the identified prepared transactions in recovery
-
- Closed
-
-
-
- Closed
-