[jira] [Updated] (SOLR-14635) improve ThreadDumpHandler to show more info related to locks

["Chris M. Hostetter (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-14635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris M. Hostetter updated SOLR-14635:
--------------------------------------
    Attachment: SOLR-14635.patch
      Assignee: Chris M. Hostetter
        Status: Open  (was: Open)

patch with test

> improve ThreadDumpHandler to show more info related to locks
> ------------------------------------------------------------
>
>                 Key: SOLR-14635
>                 URL: https://issues.apache.org/jira/browse/SOLR-14635
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Chris M. Hostetter
>            Assignee: Chris M. Hostetter
>            Priority: Major
>         Attachments: SOLR-14635.patch
>
>
> Having recently spent some time trying to use ThreadDumpHandler to diagnose a "lock leak" i realized there are quite a few bits of info available from the ThreadMXBean/ThreadInfo datastcutures that are not included in the response, and i think we should add them:
> * switch from {{findMonitorDeadlockedThreads()}} to {{findDeadlockedThreads()}} to also detect deadlocks from ownable syncrhonizers (ie: ReintrantLocks)
> * for each thread:
> ** in addition to outputing the current {{getLockName()}} when a thread is blocked/waiting, return info about the lock owner when available.
> *** there's already dead code checking this and then throwing away the info
> ** return the list of all locks (both monitors and ownable synchronizers) held by each thread



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org