Details
-
Improvement
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
Execution Team 2022-02-21
-
(copied to CRM)
Description
We perform a fatal assertion if recovering to stable timestamp returns a non-OK status from the storage engine layer. One scenario this can occur is if there is somehow an active storage transaction when attempting to do so. In order to help with diagnosis in case this happens, we should consider looking into dumping any active storage transactions if we receive a non-OK status here.
Attachments
Issue Links
- related to
-
WT-7975 [4.2.14] fix "rollback_to_stable illegal with active transactions" errors
-
- Backlog
-