[SERVER-34334] Update Locker _threadId when stashing/unstashing Created: 05/Apr/18  Updated: 29/Oct/23  Resolved: 18/Apr/18

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

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: James Wahlin
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2018-04-09, Storage NYC 2018-04-23
Participants:
Linked BF Score: 13

 Description   

For debugging, the Locker class has a _threadId member that is displayed when the lock manager dumps a lock report. To avoid confusion when using the report for diagnosis, we should ensure that this member is updated when Lockers are taken out of their originating OperationContext and stashed, and then updated again when unstashed and assigned to a new thread with a new OperationContext.



 Comments   
Comment by Githook User [ 18/Apr/18 ]

Author:

{'name': 'James Wahlin', 'username': 'jameswahlin', 'email': 'james@mongodb.com'}

Message: SERVER-34334 Update Locker _threadId when stashing/unstashing
Branch: master
https://github.com/mongodb/mongo/commit/adcbe28e5c66d0e6fc108073cf15f3fc4e078b4d

Comment by Eric Milkie [ 05/Apr/18 ]

The script in buildscripts/gdb/mongo_lock.py is what attempts to parse the output. I took a quick glance and I think it won't need any changes even if we change a stashed Locker's _threadId to simply the Locker's id value (to keep them unique in the display).

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