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

stack commented on HBASE-9022:
------------------------------

This tests still fails.

http://54.241.6.143/job/HBase-0.95-Hadoop-2/687/org.apache.hbase$hbase-server/testReport/junit/org.apache.hadoop.hbase.regionserver.wal/TestHLogSplit/testIOEOnOutputThread/

http://54.241.6.143/job/HBase-TRUNK-Hadoop-2/org.apache.hbase$hbase-server/420/testReport/org.apache.hadoop.hbase.regionserver.wal/TestHLogSplit/testIOEOnOutputThread/

http://54.241.6.143/job/HBase-TRUNK-Hadoop-2/org.apache.hbase$hbase-server/418/testReport/junit/org.apache.hadoop.hbase.regionserver.wal/TestHLogSplit/testIOEOnOutputThread/

http://54.241.6.143/job/HBase-TRUNK-Hadoop-2/org.apache.hbase$hbase-server/418/testReport/junit/org.apache.hadoop.hbase.regionserver.wal/TestHLogSplit/testIOEOnOutputThread/

... and its compressed version here:

https://builds.apache.org/view/H-L/view/HBase/job/hbase-0.95-on-hadoop2/191/testReport/junit/org.apache.hadoop.hbase.regionserver.wal/TestHLogSplitCompressed/testSplitWillFailIfWritingToRegionFails/


Usually the test completes in a couple of seconds.

When it goes > 300seconds, we are not closing one of our writers.  It is 
sticking around.  It is not a daemon thread I suppose because we want to make 
sure our edits all go in.  So, it is stuck somewhere.  I can't see it at 
momemnt.  Looking....
                
> TestHLogSplit.testIOEOnOutputThread fails
> -----------------------------------------
>
>                 Key: HBASE-9022
>                 URL: https://issues.apache.org/jira/browse/HBASE-9022
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>         Attachments: 9022.txt, 9022.txt, 9022.txt
>
>
> https://builds.apache.org/job/PreCommit-HBASE-Build/6428//testReport/org.apache.hadoop.hbase.regionserver.wal/TestHLogSplit/testIOEOnOutputThread/

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