[
https://issues.apache.org/jira/browse/SOLR-14635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17154957#comment-17154957
]
ASF subversion and git services commented on SOLR-14635:
--------------------------------------------------------
Commit a2f49eec89180357c07154e6979dff9431369124 in lucene-solr's branch
refs/heads/branch_8x from Chris M. Hostetter
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=a2f49ee ]
SOLR-14635: ThreadDumpHandler has been enhanced to show lock ownership
(cherry picked from commit 5c6314a970f9a6a07aee5a14851f3b0f9fbe02fb)
> 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: [email protected]
For additional commands, e-mail: [email protected]