Currently, we hit this invariant in WiredTigerRecoveryUnit if a rollback handler accidentally reopens the transaction. This invariant is triggered after all the rollback handlers have run, making it hard to identify the errant handler. As a rule, commit and rollback handlers should avoid accessing the OperationContext and RecoveryUnit.
It would be useful for debugging to abort at the point where the rollback/commit handler is attempting to reopen the transaction.
- is related to
-
SERVER-38069 Plan cache maintenance after rolling back index build mistakenly re-opens WT transaction
-
- Closed
-
- related to
-
SERVER-38397 make WiredTigerRecoveryUnit::State a general concept in RecoveryUnit
-
- Closed
-