[SERVER-40780] LockManager dump should show the name of global resources Created: 23/Apr/19  Updated: 06/Dec/22  Resolved: 11/Oct/19

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

Type: Improvement Priority: Minor - P4
Reporter: William Schultz (Inactive) Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Duplicate Votes: 0
Labels: tig-hanganalyzer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-39860 Separate reporting of RSTL and PBWM l... Closed
Related
related to SERVER-43910 include Client/OpCtx information in L... Closed
Assigned Teams:
Server Tooling & Methods
Participants:

 Description   

Currently, the LockManager::dump method only displays the resource id's of global resources:

2019-04-23T15:24:31.890+0000 I  -        [initandlisten] Lock @ 0x7F51BC3F9600: {2305843009213693953: Global, 1}
2019-04-23T15:24:31.890+0000 I  -        [initandlisten] Lock @ 0x7F51BC3F9680: {2305843009213693954: Global, 2}
2019-04-23T15:24:31.890+0000 I  -        [initandlisten] Lock @ 0x7F51BC3F9700: {2305843009213693955: Global, 3}

Remembering what each global lock id corresponds to is a manual translation process that is easy to forget. It would be helpful if the dump displayed a string along with the numeric id that identified the lock type e.g. Global, RSTL, or PBWM.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 11/Oct/19 ]

Yes, this is resolved by SERVER-39860, where we split the RSTL and PBWM locks off of global into their own concept: they now have names like ParallelBatchWriterMode and ReplicationStateTransition. The change is present in versions v4.2+

Comment by Benety Goh [ 10/Oct/19 ]

dianna.hohensee, do you think this issue has been fixed in SERVER-39860?

Generated at Thu Feb 08 04:55:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.