[ 
https://issues.apache.org/jira/browse/HBASE-7086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489581#comment-13489581
 ] 

Ted Yu commented on HBASE-7086:
-------------------------------

Here is sample output from TestHFileCleaner-output in 0.94 branch:
{code}
2012-11-02 10:18:59,231 INFO  [main] hbase.ResourceChecker(157): before 
master.cleaner.TestHFileCleaner#testTTLCleaner: 43 threads, 145 file 
descriptors 0 connections,

2012-11-02 10:18:59,297 DEBUG [main] cleaner.TimeToLiveHFileCleaner(68): 
Life:117, ttl:100, current:1351876739296, from: 1351876739179

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?-

2012-11-02 10:18:59,299 INFO  [main] hbase.ResourceChecker(180): after 
master.cleaner.TestHFileCleaner#testTTLCleaner: potentially hanging thread

2012-11-02 10:18:59,300 INFO  [main] hbase.ResourceChecker(186):  
java.lang.Thread.sleep(Native Method)

2012-11-02 10:18:59,300 INFO  [main] hbase.ResourceChecker(186):  
org.apache.hadoop.hdfs.DFSClient$LeaseChecker.run(DFSClient.java:1379)

2012-11-02 10:18:59,301 INFO  [main] hbase.ResourceChecker(186):  
java.lang.Thread.run(Thread.java:680)

2012-11-02 10:18:59,305 INFO  [main] hbase.ResourceChecker(157): before 
master.cleaner.TestHFileCleaner#testHFileCleaning: 44 threads, 145 file 
descriptors 0 connections,
{code}
Current goal is to figure out why TestHFileCleaner#testTTLCleaner hangs in 0.94

Trunk patch would be quite different from 0.94 patch.
                
> 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

Reply via email to