diff options
| author | Ryan Blue <blue@apache.org> | 2016-11-02 00:08:30 -0700 |
|---|---|---|
| committer | Reynold Xin <rxin@databricks.com> | 2016-11-02 00:08:30 -0700 |
| commit | 2dc048081668665f85623839d5f663b402e42555 (patch) | |
| tree | 19a6cc009b1dcd8b317a951b7ad6ba6cd8e232bd /examples | |
| parent | 85c5424d466f4a5765c825e0e2ab30da97611285 (diff) | |
| download | spark-2dc048081668665f85623839d5f663b402e42555.tar.gz spark-2dc048081668665f85623839d5f663b402e42555.tar.bz2 spark-2dc048081668665f85623839d5f663b402e42555.zip | |
[SPARK-17532] Add lock debugging info to thread dumps.
## What changes were proposed in this pull request?
This adds information to the web UI thread dump page about the JVM locks
held by threads and the locks that threads are blocked waiting to
acquire. This should help find cases where lock contention is causing
Spark applications to run slowly.
## How was this patch tested?
Tested by applying this patch and viewing the change in the web UI.
Additions:
- A "Thread Locking" column with the locks held by the thread or that are blocking the thread
- Links from the a blocked thread to the thread holding the lock
- Stack frames show where threads are inside `synchronized` blocks, "holding Monitor(...)"
Author: Ryan Blue <blue@apache.org>
Closes #15088 from rdblue/SPARK-17532-add-thread-lock-info.
Diffstat (limited to 'examples')
0 files changed, 0 insertions, 0 deletions