[SERVER-42447] Attach backtrace to waitingForLatch Created: 26/Jul/19  Updated: 29/Oct/23  Resolved: 05/Aug/19

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

Type: Improvement Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Shaileja Jain (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-41363 Add waitingForLatch field to currentOp Closed
depends on SERVER-41364 Allow generation of compressed stack ... Closed
depends on SERVER-42363 Add test for backtrace on $currentOp Closed
Backwards Compatibility: Fully Compatible
Sprint: Service Arch 2019-08-12
Participants:

 Description   

There was a mild ordering issue between SERVER-41363 and SERVER-41364. We've now landed both, so we can add the backtrace field to waitingForLatch. The output of the backtrace field should be compatible with mongosymb.py.



 Comments   
Comment by Githook User [ 05/Aug/19 ]

Author:

{'name': 'Shaileja Jain', 'username': 'shailejajain', 'email': 'shaileja.jain@gmail.com'}

Message: SERVER-42447 Add backtrace field to waitingforLatch
Branch: master
https://github.com/mongodb/mongo/commit/41da4f253c73e93df42858db48ed593c5802a2f2

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