You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jimmy Xiang (JIRA)" <ji...@apache.org> on 2012/11/12 23:37:12 UTC
[jira] [Commented] (HBASE-7152)
testShouldCheckMasterFailOverWhenMETAIsInOpenedState times out occasionally
[ https://issues.apache.org/jira/browse/HBASE-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495707#comment-13495707 ]
Jimmy Xiang commented on HBASE-7152:
------------------------------------
After startMiniHBaseCluster, the test assumes the failover is completed. Actually, it may not. We just know the meta table is assigned after startMiniHBaseCluster. User regions may have not started to assign yet, depending on the timing. In this case, there is no region in transition yet.
> testShouldCheckMasterFailOverWhenMETAIsInOpenedState times out occasionally
> ---------------------------------------------------------------------------
>
> Key: HBASE-7152
> URL: https://issues.apache.org/jira/browse/HBASE-7152
> Project: HBase
> Issue Type: Test
> Components: test
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Priority: Minor
> Attachments: trunk-7152.patch
>
>
> {noformat}
> java.lang.Exception: test timed out after 180000 milliseconds
> at java.lang.Throwable.fillInStackTrace(Native Method)
> at java.lang.Throwable.<init>(Throwable.java:181)
> at org.apache.log4j.spi.LoggingEvent.getLocationInformation(LoggingEvent.java:253)
> at org.apache.log4j.helpers.PatternParser$ClassNamePatternConverter.getFullyQualifiedName(PatternParser.java:555)
> at org.apache.log4j.helpers.PatternParser$NamedPatternConverter.convert(PatternParser.java:528)
> at org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:65)
> at org.apache.log4j.PatternLayout.format(PatternLayout.java:506)
> at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:310)
> at org.apache.log4j.WriterAppender.append(WriterAppender.java:162)
> at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251)
> at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66)
> at org.apache.log4j.Category.callAppenders(Category.java:206)
> at org.apache.log4j.Category.forcedLog(Category.java:391)
> at org.apache.log4j.Category.log(Category.java:856)
> at org.apache.commons.logging.impl.Log4JLogger.debug(Log4JLogger.java:188)
> at org.apache.hadoop.hbase.LocalHBaseCluster.join(LocalHBaseCluster.java:407)
> at org.apache.hadoop.hbase.MiniHBaseCluster.join(MiniHBaseCluster.java:408)
> at org.apache.hadoop.hbase.HBaseTestingUtility.shutdownMiniHBaseCluster(HBaseTestingUtility.java:599)
> at org.apache.hadoop.hbase.HBaseTestingUtility.shutdownMiniCluster(HBaseTestingUtility.java:573)
> at org.apache.hadoop.hbase.master.TestMasterFailover.testShouldCheckMasterFailOverWhenMETAIsInOpenedState(TestMasterFailover.java:113)
> 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:45)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:62)
> {noformat}
--
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