Details
-
Bug
-
Status: Closed
-
Critical - P2
-
Resolution: Fixed
-
4.1.1
-
Fully Compatible
-
TIG 2018-08-13
-
0
-
2
Description
In BF-9986, we saw many threads waiting on DB locks, but the hang analyzer cannot generate the graph for us. The lock manager dumps the information though.
[2018/07/18 12:40:44.821] warning: target file /proc/17238/cmdline contained unexpected null characters
|
[2018/07/18 12:40:44.821] Saved corefile dump_mongod.17238.core
|
[2018/07/18 12:41:07.364] Running Hang Analyzer Supplement - MongoDBDumpLocks
|
[2018/07/18 12:41:07.364] Not generating the digraph, since the lock graph is empty
|
[2018/07/18 12:41:07.364] Running Print JavaScript Stack Supplement
|
[2018/07/18 12:41:07.364] Detaching from program: /data/mci/d8572849d2ad8ce1953117503927f065/src/mongod, process 17238
|
[2018/07/18 12:41:07.491] Done analyzing mongod process with PID 17238
|
[2018/07/18 12:41:07.491] Debugger /opt/mongodbtoolchain/gdb/bin/gdb, analyzing mongod process with PID 17241
|
Attachments
Issue Links
- is caused by
-
SERVER-36011 remove MMAPv1 support from the lock manager
-
- Closed
-
- related to
-
SERVER-36356 Improve test coverage for hang analyzer script to cover waits-for scenario
-
- Closed
-