[SERVER-58655] Dump active storage transactions before StorageInterfaceImpl::recoverToStableTimestamp fatal assertion Created: 19/Jul/21  Updated: 29/Oct/23  Resolved: 16/Feb/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.3.0-rc1

Type: Improvement Priority: Major - P3
Reporter: Gregory Noma Assignee: Haley Connelly
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to WT-7975 [4.2.14] fix "rollback_to_stable ille... Backlog
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-02-21
Participants:
Case:

 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.



 Comments   
Comment by Githook User [ 16/Feb/22 ]

Author:

{'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}

Message: SERVER-58655 dump active storage transactions before StorageInterfaceImpl::recoverToStableTimestamp fatal assertion
Branch: master
https://github.com/mongodb/mongo/commit/aba3de62beaef104fd666f27222955a1593029a6

Comment by Haley Connelly [ 14/Feb/22 ]

agorrod 

"Is there a way MongoDB could dump the active transactions before the fassert to get more information about what operation is active?"

Is WiredTigerKVEngine::dump() what we are looking for? — it calls debug_info with txn=true

The method calls

 

_conn->debug_info(_conn, "cursors=true,handles=true,log=true,sessions=true,txn=true");

 

Or are we looking to somehow iterate over the active transactions tracked by the MongoDB server rather than the storage engine itself?

If there is no opinion, we will just go with the engine dump

Generated at Thu Feb 08 05:45:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.