[ https://issues.apache.org/jira/browse/HBASE-7086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490378#comment-13490378 ]
Hudson commented on HBASE-7086: ------------------------------- Integrated in HBase-0.94-security-on-Hadoop-23 #9 (See [https://builds.apache.org/job/HBase-0.94-security-on-Hadoop-23/9/]) HBASE-7086 Enhance ResourceChecker to log stack trace for potentially hanging threads, addendum (Revision 1405207) HBASE-7086 Enhance ResourceChecker to log stack trace for potentially hanging threads (Revision 1405081) Result = FAILURE tedyu : Files : * /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/ResourceChecker.java tedyu : Files : * /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/ResourceChecker.java * /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/ResourceCheckerJUnitRule.java > 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 > Assignee: Ted Yu > Fix For: 0.94.3, 0.96.0 > > Attachments: 7086.94, 7086-94.addendum, 7086-trunk.txt, > 7086-trunk-v2.txt, 7086-trunk-v3.txt, testHFileCleaner.out > > > 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