hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19927) TestFullLogReconstruction flakey
Date Sun, 04 Feb 2018 00:43:00 GMT

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

Duo Zhang commented on HBASE-19927:
-----------------------------------

And I think we should enable TestDLSFSHLog and TestDLSAsyncFSWAL again to fix them also?

> TestFullLogReconstruction flakey
> --------------------------------
>
>                 Key: HBASE-19927
>                 URL: https://issues.apache.org/jira/browse/HBASE-19927
>             Project: HBase
>          Issue Type: Sub-task
>          Components: wal
>            Reporter: stack
>            Priority: Major
>             Fix For: 2.0.0-beta-2
>
>
> Fails pretty frequently in hadoopqa builds.
> There is a recent hang in org.apache.hadoop.hbase.TestFullLogReconstruction.tearDownAfterClass(TestFullLogReconstruction.java:68)
> In here... https://builds.apache.org/job/PreCommit-HBASE-Build/11363/testReport/org.apache.hadoop.hbase/TestFullLogReconstruction/org_apache_hadoop_hbase_TestFullLogReconstruction/
> ... see here.
> Thread 1250 (RS_CLOSE_META-edd281aedb18:59863-0):
>   State: TIMED_WAITING
>   Blocked count: 92
>   Waited count: 278
>   Stack:
>     java.lang.Object.wait(Native Method)
>     org.apache.hadoop.hbase.regionserver.wal.SyncFuture.get(SyncFuture.java:133)
>     org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.blockOnSync(AbstractFSWAL.java:718)
>     org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.sync(AsyncFSWAL.java:605)
>     org.apache.hadoop.hbase.regionserver.wal.WALUtil.doFullAppendTransaction(WALUtil.java:154)
>     org.apache.hadoop.hbase.regionserver.wal.WALUtil.writeFlushMarker(WALUtil.java:81)
>     org.apache.hadoop.hbase.regionserver.HRegion.internalFlushCacheAndCommit(HRegion.java:2645)
>     org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2356)
>     org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2328)
>     org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:2319)
>     org.apache.hadoop.hbase.regionserver.HRegion.doClose(HRegion.java:1531)
>     org.apache.hadoop.hbase.regionserver.HRegion.close(HRegion.java:1437)
>     org.apache.hadoop.hbase.regionserver.handler.CloseRegionHandler.process(CloseRegionHandler.java:104)
>     org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:104)
>     java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>     java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>     java.lang.Thread.run(Thread.java:748)
> We missed a signal? We need to do an interrupt? The log is not all there in hadoopqa
builds so hard to see all that is going on. This test is not in the flakey set either....



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message