GitHub user rdblue opened a pull request:

    https://github.com/apache/spark/pull/15088

    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.
    
    
![thread-lock-info](https://cloud.githubusercontent.com/assets/87915/18493057/6e5da870-79c3-11e6-8c20-f54c18a37544.png)
    
    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(...)"


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/rdblue/spark SPARK-17532-add-thread-lock-info

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/15088.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #15088
    
----
commit f49b6aaf767ee38280998984e0c180f2be5d8724
Author: Ryan Blue <b...@apache.org>
Date:   2016-09-12T20:52:11Z

    SPARK-17532: Add lock debugging info to thread dumps.
    
    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.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to