[SERVER-53745] Improve lock identification information logged on lock timeout errors Created: 13/Jan/21  Updated: 06/Dec/22  Resolved: 21/Jan/21

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-53415 Intent Lock timeout lead to server crash Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

LockerImpl::lock() is called by code that appears to typically have a dbName or nss or UUID. However, down in LockerImpl::_lockComplete() where we log "Unable to acquire ... lock on <resId> within <time>", we only provide a hard/impossible to identify resId number. It would be helpful to connect the name for the lock down through to this log message, so we can know what lock failed to be acquired.

I'm less familiar with ResourceMutex identification, but it would be great to improve identification logging for those as well – an ambiguous resId number for a ResourceMutex acquisition attempt is what motivated this ticket.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 21/Jan/21 ]

Closing. This would need more investigation of what we already do, to see what we could improve.

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