hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9023) TestIOFencing.testFencingAroundCompactionAfterWALSync occasionally fails
Date Sun, 18 Aug 2013 03:13:47 GMT

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

Ted Yu commented on HBASE-9023:
-------------------------------

It turns out that flush detection logic still needs to be refined.
In one test run, here was the first completion of flush:
{code}
2013-08-17 15:10:18,370 INFO  [Thread-282] regionserver.HStore(760): Added hdfs://localhost.localdomain:53662/user/jenkins/hbase/data/default/tabletest/174fab922ef8fceeb0342279c97aadb7/family/4f528c163ab64226829fd13b7ae3f4b0,
entries=2319, sequenceid=2323, filesize=77.9 K
2013-08-17 15:10:18,370 INFO  [Thread-282] regionserver.HRegion(1639): Finished memstore flush
of ~390.8 K/400144, currentsize=0/0 for region tabletest,,1376777411816.174fab922ef8fceeb0342279c97aadb7.
in 651ms, sequenceid=2323, compaction requested=false
{code}
However, the test failed with:
{code}
java.lang.AssertionError: lastFlushTime: 1376777411967 current: 1376777418370
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.apache.hadoop.hbase.TestIOFencing.doTest(TestIOFencing.java:264)
	at org.apache.hadoop.hbase.TestIOFencing.testFencingAroundCompactionAfterWALSync(TestIOFencing.java:218)
{code}
1376777418370, in milliseconds, corresponds to 2013-08-17 15:10:18.
Obviously the reading of 1376777411967 as the previous flush time was incorrect. It was due
to the assignment in HRegion#initializeRegionInternals():
{code}
    this.lastFlushTime = EnvironmentEdgeManager.currentTimeMillis();
{code}
                
> TestIOFencing.testFencingAroundCompactionAfterWALSync occasionally fails
> ------------------------------------------------------------------------
>
>                 Key: HBASE-9023
>                 URL: https://issues.apache.org/jira/browse/HBASE-9023
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: Ted Yu
>             Fix For: 0.98.0, 0.96.0
>
>         Attachments: 9023-v1.txt
>
>
> Any one want to take a look at this one? 
> https://builds.apache.org/job/HBase-TRUNK/4283/testReport/org.apache.hadoop.hbase/TestIOFencing/testFencingAroundCompactionAfterWALSync/
> {code}
> java.lang.AssertionError
> 	at org.junit.Assert.fail(Assert.java:86)
> 	at org.junit.Assert.assertTrue(Assert.java:41)
> 	at org.junit.Assert.assertTrue(Assert.java:52)
> 	at org.apache.hadoop.hbase.TestIOFencing.doTest(TestIOFencing.java:263)
> 	at org.apache.hadoop.hbase.TestIOFencing.testFencingAroundCompactionAfterWALSync(TestIOFencing.java:217)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> 	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> 	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> 	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> 	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> 	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> 	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> 	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> 	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> 	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> 	at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> 	at org.junit.runners.Suite.runChild(Suite.java:127)
> 	at org.junit.runners.Suite.runChild(Suite.java:26)
> 	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> 	at java.lang.Thread.run(Thread.java:662)
> {code}

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

Mime
View raw message