hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9168) TestMetaMigrationConvertingToPB fails on hadoop 2.0 due to FileNotFoundException
Date Fri, 09 Aug 2013 06:25:48 GMT

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

stack commented on HBASE-9168:

Here is example:$hbase-server/438/testReport/junit/org.apache.hadoop.hbase.catalog/TestMetaMigrationConvertingToPB/org_apache_hadoop_hbase_catalog_TestMetaMigrationConvertingToPB/

java.io.FileNotFoundException: File hdfs://localhost:35352/user/ec2-user/hbase/.archive does
not exist.
	at org.apache.hadoop.hdfs.DistributedFileSystem.listStatus(DistributedFileSystem.java:405)
	at org.apache.hadoop.fs.FileSystem.listStatus(FileSystem.java:1430)
	at org.apache.hadoop.fs.FileSystem.listStatus(FileSystem.java:1470)
	at org.apache.hadoop.hbase.util.FSUtils.getLocalTableDirs(FSUtils.java:1317)

We are passing in a dir that does not exist (.archive)?  NameSpaceUpgrade shouldn't do that.
 Should test for existence before proceeding.
> TestMetaMigrationConvertingToPB fails on hadoop 2.0 due to FileNotFoundException
> --------------------------------------------------------------------------------
>                 Key: HBASE-9168
>                 URL: https://issues.apache.org/jira/browse/HBASE-9168
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>         Attachments: 9168-v1.txt
> NamespaceUpgrade is called by TestMetaMigrationConvertingToPB
> TestMetaMigrationConvertToPB.tgz doesn't contain .archive directory.
> NamespaceUpgrade#migrateTables() calls listStatus() on .archive directory (hardcoded)
> Due to change of behavior in hadoop 2.0, FileNotFoundException gets thrown and makes
the test fail.

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

View raw message