[SERVER-39116] Name unnamed GlobalLock in TransactionParticipant Created: 22/Jan/19  Updated: 29/Oct/23  Resolved: 03/Jun/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.2.0-rc1, 4.3.1

Type: Improvement Priority: Major - P3
Reporter: Judah Schvimer Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: prepare_optional
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Backport Completed:
Backport Requested:
v4.2
Sprint: Repl 2019-06-03, Repl 2019-06-17
Participants:
Linked BF Score: 69

 Description   

This GlobalLock is unnamed. This is not a bug due to two-phase-locking, but it does make debugging deadlocks more difficult since there is no variable to inspect in a core dump.



 Comments   
Comment by Githook User [ 06/Jun/19 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com'}

Message: SERVER-39116 Name unnamed GlobalLock in TransactionParticipant

(cherry picked from commit 88f2b4c6cbe7c06e20f1638c4aeced5d9dfeeea7)
Branch: v4.2
https://github.com/mongodb/mongo/commit/b9677eb4b98fba42c92e97a70eb58b812db1ce7a

Comment by Githook User [ 03/Jun/19 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com'}

Message: SERVER-39116 Name unnamed GlobalLock in TransactionParticipant
Branch: master
https://github.com/mongodb/mongo/commit/88f2b4c6cbe7c06e20f1638c4aeced5d9dfeeea7

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