[SERVER-68907] Dump WiredTiger information on EBUSY before fatal assertions Created: 17/Aug/22  Updated: 29/Oct/23  Resolved: 06/Sep/22

Status: Closed
Project: Core Server
Component/s: Diagnostics
Affects Version/s: 4.4.16, 4.2.22
Fix Version/s: 6.2.0-rc0

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

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-09-19
Participants:

 Description   

There are a few places where the server will hit a fatal assertion when EBUSY is returned from WiredTiger, such as alter and rollback to stable.

We should dump the WiredTiger information to help us diagnose the cause of this unexpected behaviour. SERVER-61177/WT-3529 added an API to dump WiredTiger system info, which we can make use of for this.



 Comments   
Comment by Githook User [ 06/Sep/22 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-68907 Dump WiredTiger information on EBUSY before fatal assertions
Branch: master
https://github.com/mongodb/mongo/commit/5fa151ad8b9d80f95263216edec292614ad07034

Generated at Thu Feb 08 06:12:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.