[ https://issues.apache.org/jira/browse/HBASE-7086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489571#comment-13489571 ]
stack commented on HBASE-7086: ------------------------------ Does it work? Does it retain the above resource checker log line and list the difference in threads after this logging? How we make this work in trunk? I like stuff like this that gives more info when testing. > Enhance ResourceChecker to log stack trace for potentially hanging threads > -------------------------------------------------------------------------- > > Key: HBASE-7086 > URL: https://issues.apache.org/jira/browse/HBASE-7086 > Project: HBase > Issue Type: Bug > Reporter: Ted Yu > Attachments: 7086.94 > > > Currently ResourceChecker logs a line similar to the following if it detects > potential thread leak: > {code} > 2012-11-02 10:18:59,299 INFO [main] hbase.ResourceChecker(157): after > master.cleaner.TestHFileCleaner#testTTLCleaner: 44 threads (was 43), 145 file > descriptors (was 145). 0 connections, -thread leak?- > {code} > We should enhance the log to include stack trace of the potentially hanging > thread(s) > This work was motivated when I investigated test failure in HBASE-6796 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira