[SERVER-28198] Remove the decimal format for threadId when dumping LockManager Created: 06/Mar/17  Updated: 06/Dec/22  Resolved: 11/May/20

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

Type: Task Priority: Minor - P4
Reporter: Eddie Louie Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Won't Fix Votes: 0
Labels: stm
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-27866 The globalLockManager dump should pri... Closed
Assigned Teams:
Server Tooling & Methods
Participants:

 Description   

Currently in the LockManager::_dumpBucket function we dump the decimal and hexadecimal format for the threadId. We should simplify this and only dump the hex value.

The output should look like:

GRANTED:
LockRequest 293 @ 0x5592FBF23000: Mode = X; Thread = 0x7f17d425b700; ConvertMode = NONE; EnqueueAtFront = 0; CompatibleFirst = 0;
PENDING:
LockRequest 294 @ 0x5592FBF23C00: Mode = S; Thread = 0x7f17c0132700; ConvertMode = NONE; EnqueueAtFront = 0; CompatibleFirst = 0;



 Comments   
Comment by Ryan Timmons [ 11/May/20 ]

Closing as wont-fix to indicate that there is currently no intention of doing this. Please re-open if there is priority for this. Perhaps this change could self-service by an appropriate server team if this is necessary rather than having to go thru the STM prioritization queue.

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