[SERVER-28348] Detect single-process deadlocks involving LockManager locks and/or pthread_mutexes Created: 16/Mar/17  Updated: 06/Dec/17  Resolved: 21/Apr/17

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

Type: Improvement Priority: Major - P3
Reporter: Jonathan Abrahams Assignee: Jonathan Abrahams
Resolution: Done Votes: 0
Labels: bkp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-27874 Display locks and generate digraph fo... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.4
Sprint: TIG 2017-04-17, TIG 2017-05-08
Participants:

 Description   

Add logic to detect the deadlock from the digraph generated in SERVER-27874



 Comments   
Comment by Githook User [ 28/Apr/17 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-28348 Detect single-process deadlocks involving LockManager locks and/or pthread_mutexes
SERVER-28348 Add cycle detect message for detecting single-process deadlocks involving LockManager locks and/or pthread_mutexes

(cherry picked from commit d4c16656d746c9e7a76579b593c41e48c915025d)
(cherry picked from commit c2cb98f46c70772d054ab0885720b666ae318cf0)
Branch: v3.4
https://github.com/mongodb/mongo/commit/b389af851cb5b615e15210ab44b717936f43feb3

Comment by Githook User [ 28/Apr/17 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-28348 Detect single-process deadlocks involving LockManager locks and/or pthread_mutexes
SERVER-28348 Add cycle detect message for detecting single-process deadlocks involving LockManager locks and/or pthread_mutexes

(cherry picked from commit d4c16656d746c9e7a76579b593c41e48c915025d)
(cherry picked from commit c2cb98f46c70772d054ab0885720b666ae318cf0)
Branch: v3.4
https://github.com/mongodb/mongo/commit/b389af851cb5b615e15210ab44b717936f43feb3

Comment by Githook User [ 21/Apr/17 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-28348 Add cycle detect message for detecting single-process deadlocks involving LockManager locks and/or pthread_mutexes
Branch: master
https://github.com/mongodb/mongo/commit/c2cb98f46c70772d054ab0885720b666ae318cf0

Comment by Jonathan Abrahams [ 21/Apr/17 ]

We will add a message that the cycle has been detected, which can be costumed by the log extractor.

Comment by Githook User [ 20/Apr/17 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-28348 Detect single-process deadlocks involving LockManager locks and/or pthread_mutexes
Branch: master
https://github.com/mongodb/mongo/commit/d4c16656d746c9e7a76579b593c41e48c915025d

Comment by Max Hirschhorn [ 23/Mar/17 ]

Until SERVER-28437 is implemented, the hang analyzer won't be able to definitively say that a process has a cycle in the waits-for graph. We may want to hold off on this for now until more research into SERVER-28437 has been done.

The digraph files generated by the mongodb-waitsfor-graph GDB command appear to be sufficient for Build Barons that I see this as mainly for aided automated de-duplication of failures.

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