[SERVER-78171] Get the DDL operation that holds a DDL lock on LockTimeout exception Created: 16/Jun/23  Updated: 29/Oct/23  Resolved: 12/Jul/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Silvia Surroca Assignee: Silvia Surroca
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Backwards Compatibility: Major Change
Sprint: Sharding EMEA 2023-07-10, Sharding EMEA 2023-07-24
Participants:

 Description   

With the recent changes done on DDLLockManager to use LockManager instead of self-manage DDL locks, we have lost the ability to know which DDL operation is holding the given resource when a LockTimeout exception is thrown during a DDL lock acquisition.

The aim of this ticket is to investigate and implement a way of getting that information and print it out once a LockTimeout raises, as well as the old DDLLockManager did here.



 Comments   
Comment by Githook User [ 12/Jul/23 ]

Author:

{'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}

Message: SERVER-77512 SERVER-78171 Improve diagnosticability for DDL locks
Branch: master
https://github.com/mongodb/mongo/commit/1df6a1b3318b2634cf38c22f775d1e494933ebda

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