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/12/21 20:47:12 UTC
[jira] [Resolved] (HBASE-7421) TestHFileCleaner->testHFileCleaning
has an aggressive timeout
[ https://issues.apache.org/jira/browse/HBASE-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jimmy Xiang resolved HBASE-7421.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.96.0
Hadoop Flags: Reviewed
Integrated into trunk and 0.94. Thanks Matteo for the review, Himanshu for the patch.
> TestHFileCleaner->testHFileCleaning has an aggressive timeout
> --------------------------------------------------------------
>
> Key: HBASE-7421
> URL: https://issues.apache.org/jira/browse/HBASE-7421
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 0.94.3
> Reporter: Himanshu Vashishtha
> Assignee: Himanshu Vashishtha
> Priority: Minor
> Fix For: 0.96.0, 0.94.4
>
> Attachments: HBASE-7421.patch
>
>
> As the description, increasing it to 1 min to have some upper limit.
> {code}
> FAILED: org.apache.hadoop.hbase.master.cleaner.TestHFileCleaner.testHFileCleaning
> Error Message:
> test timed out after 2000 milliseconds
> Stack Trace:
> java.lang.Exception: test timed out after 2000 milliseconds
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:485)
> at org.apache.hadoop.ipc.Client.call(Client.java:1210)
> at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:202)
> at $Proxy17.create(Unknown Source)
> at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:164)
> at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:83)
> at $Proxy17.create(Unknown Source)
> at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.create(ClientNamenodeProtocolTranslatorPB.java:192)
> at org.apache.hadoop.hdfs.DFSOutputStream.<init>(DFSOutputStream.java:1298)
> at org.apache.hadoop.hdfs.DFSOutputStream.newStreamForCreate(DFSOutputStream.java:1317)
> at org.apache.hadoop.hdfs.DFSClient.create(DFSClient.java:1243)
> at org.apache.hadoop.hdfs.DFSClient.create(DFSClient.java:1200)
> at org.apache.hadoop.hdfs.DistributedFileSystem.create(DistributedFileSystem.java:273)
> at org.apache.hadoop.hdfs.DistributedFileSystem.create(DistributedFileSystem.java:262)
> at org.apache.hadoop.hdfs.DistributedFileSystem.create(DistributedFileSystem.java:79)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:811)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:792)
> at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:754)
> at org.apache.hadoop.fs.FileSystem.createNewFile(FileSystem.java:1054)
> at org.apache.hadoop.hbase.master.cleaner.TestHFileCleaner.testHFileCleaning(TestHFileCleaner.java:119)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> {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