[SERVER-39244] Improve hang analyzer logging around idle transactions Created: 29/Jan/19  Updated: 06/Dec/22  Resolved: 17/May/19

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

Type: Improvement Priority: Major - P3
Reporter: Judah Schvimer Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: prepare_optional, prepare_testing, tig-hanganalyzer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Participants:

 Description   

The hang analyzer will log things like:

[2018/12/20 16:22:29.931] MongoDB Lock at 0x10024bc0c00 held by Idle Transaction (LockerId 358) (mongo::MODE_IX) waited on by "conn36" (Thread 0x3fff849deda0 (LWP 34093))

This doesn't give much information about the idle transaction. Logging the SessionID and txnNumber of the transaction, and maybe even what namespaces the statements were on would be very helpful.



 Comments   
Comment by Judah Schvimer [ 29/Jan/19 ]

This came out of a discussion I had with max.hirschhorn around improvements to the hang analyzer for deadlocks involving transactions.

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