You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Himanshu Vashishtha (JIRA)" <ji...@apache.org> on 2012/11/10 01:51:12 UTC
[jira] [Created] (HBASE-7142) TestSplitLogManager#testDeadWorker
may fail because of hard limit on the TimeoutMonitor's timeout period
Himanshu Vashishtha created HBASE-7142:
------------------------------------------
Summary: 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
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
[jira] [Resolved] (HBASE-7142) TestSplitLogManager#testDeadWorker
may fail because of hard limit on the TimeoutMonitor's timeout period
Posted by "Lars Hofhansl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl resolved HBASE-7142.
----------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Committed to 0.94. Thanks for the patch Himanshu.
> 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
> Assignee: 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
[jira] [Updated] (HBASE-7142) TestSplitLogManager#testDeadWorker
may fail because of hard limit on the TimeoutMonitor's timeout period
Posted by "Himanshu Vashishtha (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Himanshu Vashishtha updated HBASE-7142:
---------------------------------------
Attachment: HBASE-7142.patch
TestSplitLogManager passes.
> 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
[jira] [Commented] (HBASE-7142) TestSplitLogManager#testDeadWorker
may fail because of hard limit on the TimeoutMonitor's timeout period
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495010#comment-13495010 ]
Hudson commented on HBASE-7142:
-------------------------------
Integrated in HBase-0.94 #579 (See [https://builds.apache.org/job/HBase-0.94/579/])
HBASE-7142 TestSplitLogManager#testDeadWorker may fail because of hard limit on the TimeoutMonitor's timeout period (Himanshu) (Revision 1408119)
Result = SUCCESS
larsh :
Files :
* /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/master/TestSplitLogManager.java
> 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
> Assignee: 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
[jira] [Commented] (HBASE-7142) TestSplitLogManager#testDeadWorker
may fail because of hard limit on the TimeoutMonitor's timeout period
Posted by "Lars Hofhansl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494838#comment-13494838 ]
Lars Hofhansl commented on HBASE-7142:
--------------------------------------
Is this only an issue in 0.94 (but not 0.96)?
> 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
[jira] [Commented] (HBASE-7142) TestSplitLogManager#testDeadWorker
may fail because of hard limit on the TimeoutMonitor's timeout period
Posted by "Lars Hofhansl (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Assigned] (HBASE-7142) TestSplitLogManager#testDeadWorker
may fail because of hard limit on the TimeoutMonitor's timeout period
Posted by "Lars Hofhansl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl reassigned HBASE-7142:
------------------------------------
Assignee: Himanshu Vashishtha
> 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
> Assignee: 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
[jira] [Commented] (HBASE-7142) TestSplitLogManager#testDeadWorker
may fail because of hard limit on the TimeoutMonitor's timeout period
Posted by "Himanshu Vashishtha (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494846#comment-13494846 ]
Himanshu Vashishtha commented on HBASE-7142:
--------------------------------------------
Yeah, only 0.94.
The timeout in 0.96 is already set to 3 sec.
> 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
[jira] [Commented] (HBASE-7142) TestSplitLogManager#testDeadWorker
may fail because of hard limit on the TimeoutMonitor's timeout period
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496084#comment-13496084 ]
Hudson commented on HBASE-7142:
-------------------------------
Integrated in HBase-0.94-security #83 (See [https://builds.apache.org/job/HBase-0.94-security/83/])
HBASE-7142 TestSplitLogManager#testDeadWorker may fail because of hard limit on the TimeoutMonitor's timeout period (Himanshu) (Revision 1408119)
Result = SUCCESS
larsh :
Files :
* /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/master/TestSplitLogManager.java
> 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
> Assignee: 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