[SERVER-69397] Log recursiveCount and unlockPending when dumping locks Created: 02/Sep/22  Updated: 29/Oct/23  Resolved: 08/Sep/22

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

Type: Improvement Priority: Major - P3
Reporter: Jordi Olivares Provencio Assignee: Jordi Olivares Provencio
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File patch.diff    
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-09-19
Participants:

 Description   

As part of SERVER-66752 I had to modify LockerImpl::dump() to print more information to diagnose lock state from the logs. This helped identify we were in 2-phase locking.

I've included a patch with the changes made to print the missing fields.



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

Author:

{'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}

Message: SERVER-69397 Dump recursiveCount and unlockPending from locks
Branch: master
https://github.com/mongodb/mongo/commit/44c8b34f1d6d01d67e454fb2d0073d7e07cd652a

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