[ https://issues.apache.org/jira/browse/HBASE-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13716044#comment-13716044 ]
stack commented on HBASE-5995: ------------------------------ TestLogRolling.testLogRollOnPipelineRestart failed on hadoop1 here: https://builds.apache.org/job/hbase-0.95/352/consoleText It went zombie. In the double thread dump on the end: {code} "pool-1-thread-1" prio=10 tid=0x73f9dc00 nid=0x3a34 in Object.wait() [0x7517d000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0xcf624ad0> (a java.util.concurrent.atomic.AtomicLong) at org.apache.hadoop.hbase.client.AsyncProcess.waitForNextTaskDone(AsyncProcess.java:634) - locked <0xcf624ad0> (a java.util.concurrent.atomic.AtomicLong) at org.apache.hadoop.hbase.client.AsyncProcess.waitForMaximumCurrentTasks(AsyncProcess.java:659) at org.apache.hadoop.hbase.client.AsyncProcess.waitUntilDone(AsyncProcess.java:670) at org.apache.hadoop.hbase.client.HTable.backgroundFlushCommits(HTable.java:813) at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:1170) at org.apache.hadoop.hbase.client.HTable.put(HTable.java:753) at org.apache.hadoop.hbase.regionserver.wal.TestLogRolling.doPut(TestLogRolling.java:640) at org.apache.hadoop.hbase.regionserver.wal.TestLogRolling.writeData(TestLogRolling.java:248) at org.apache.hadoop.hbase.regionserver.wal.TestLogRolling.testLogRollOnPipelineRestart(TestLogRolling.java:515) {code} ... we are stuck here. The math looks like it could go wonky. But looking in the output for the test, it seems that when this test ran we got this: 2013-07-23 01:23:29,560 INFO [pool-1-thread-1] hbase.HBaseTestingUtility(922): Minicluster is down 2013-07-23 01:23:29,574 INFO [pool-1-thread-1] hbase.ResourceChecker(171): after: regionserver.wal.TestLogRolling#testLogRollOnPipelineRestart Thread=39 (was 31) - Thread LEAK? -, OpenFileDescriptor=312 (was 272) - OpenFileDescriptor LEAK? -, MaxFileDescriptor=40000 (was 40000), SystemLoadAverage=351 (was 368), ProcessCount=144 (was 142) - ProcessCount LEAK? -, AvailableMemoryMB=906 (was 1995), ConnectionCount=0 (was 0) So we were up against the fd limit. > Fix and reenable TestLogRolling.testLogRollOnPipelineRestart > ------------------------------------------------------------ > > Key: HBASE-5995 > URL: https://issues.apache.org/jira/browse/HBASE-5995 > Project: HBase > Issue Type: Sub-task > Components: test > Reporter: stack > Assignee: Enis Soztutar > Priority: Blocker > Fix For: 0.98.0, 0.95.1 > > Attachments: hbase-5995_v1.patch, hbase-5995_v2.patch, > hbase-5995_v3.patch > > > HBASE-5984 disabled this flakey test (See the issue for more). This issue is > about getting it enabled again. Made a blocker on 0.96.0 so it gets > attention. -- 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