You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2012/11/11 06:49:12 UTC
[jira] [Commented] (HBASE-7142) TestSplitLogManager#testDeadWorker
may fail because of hard limit on the TimeoutMonitor's timeout period
[ https://issues.apache.org/jira/browse/HBASE-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494831#comment-13494831 ]
Lars Hofhansl commented on HBASE-7142:
--------------------------------------
Works for me. I'll take your word that the new timeout is long enough.
> TestSplitLogManager#testDeadWorker may fail because of hard limit on the TimeoutMonitor's timeout period
> --------------------------------------------------------------------------------------------------------
>
> Key: HBASE-7142
> URL: https://issues.apache.org/jira/browse/HBASE-7142
> Project: HBase
> Issue Type: Test
> Components: test
> Affects Versions: 0.94.2
> Reporter: Himanshu Vashishtha
> Priority: Minor
> Fix For: 0.94.3
>
> Attachments: HBASE-7142.patch
>
>
> The timeout in testDeadWorker is set to 1 sec, it is the same as the TimeoutMonitor thread timeout. In some case, this may fail:
> {code}
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:92)
> at org.junit.Assert.assertTrue(Assert.java:43)
> at org.junit.Assert.assertTrue(Assert.java:54)
> at org.apache.hadoop.hbase.master.TestSplitLogManager.waitForCounter(TestSplitLogManager.java:147)
> at org.apache.hadoop.hbase.master.TestSplitLogManager.waitForCounter(TestSplitLogManager.java:127)
> at org.apache.hadoop.hbase.master.TestSplitLogManager.testDeadWorker(TestSplitLogManager.java:433)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> {code}
> Fix is to increase the timeout for this test. Its not needed in trunk as the timeout is 3 seconds.
--
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