hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Boudnik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-669) Add unit tests
Date Mon, 09 Nov 2009 20:46:32 GMT

    [ https://issues.apache.org/jira/browse/HDFS-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12775125#action_12775125

Konstantin Boudnik commented on HDFS-669:

I'm sure you've noticed that already, but the test cases are failing with the following diagnostics:
2009-11-09 12:33:37,906 INFO  metrics.FSNamesystemMetrics (FSNamesystemMetrics.java:<init>(78))
- Initializing FSNamesystemMetrics using context object:org.apache.hadoop.metrics.
2009-11-09 12:33:37,915 INFO  namenode.FSNamesystem (FSNamesystem.java:registerMBean(3991))
- Registered FSNamesystemStatusMBean
2009-11-09 12:33:37,973 WARN  conf.Configuration (Configuration.java:handleDeprecation(326))
- fs.checkpoint.dir is deprecated. Instead, use dfs.namenode.checkpoint.dir
2009-11-09 12:33:37,975 WARN  namenode.FSNamesystem (FSNamesystem.java:getStorageDirs(350))
- Scheme is undefined for /tmp/hadoop-cos/dfs/name
2009-11-09 12:33:37,975 WARN  namenode.FSNamesystem (FSNamesystem.java:getStorageDirs(351))
- Please check your file system configuration in hdfs-site.xml
2009-11-09 12:33:37,976 WARN  namenode.FSNamesystem (FSNamesystem.java:getStorageDirs(350))
- Scheme is undefined for /tmp/hadoop-cos/dfs/name
2009-11-09 12:33:37,976 WARN  namenode.FSNamesystem (FSNamesystem.java:getStorageDirs(351))
- Please check your file system configuration in hdfs-site.xml
2009-11-09 12:33:37,981 INFO  common.Storage (Storage.java:analyzeStorage(356)) - Storage
directory /private/tmp/hadoop-cos/dfs/name does not exist.
2009-11-09 12:33:37,985 ERROR namenode.FSNamesystem (FSNamesystem.java:<init>(244))
- FSNamesystem initialization failed.
org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /private/tmp/hadoop-cos/dfs/name
is in an inconsistent state: storage directory does not exist or is 
not accessible.
        at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:401)
        at org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirectory.java:112)
        at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:261)
        at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:242)
        at org.apache.hadoop.hdfs.server.namenode.TestFSNamesystem.getNamesystem(TestFSNamesystem.java:49)
        at org.apache.hadoop.hdfs.server.namenode.TestFSNamesystem.testRenameInSafemode(TestFSNamesystem.java:54)

> Add unit tests 
> ---------------
>                 Key: HDFS-669
>                 URL: https://issues.apache.org/jira/browse/HDFS-669
>             Project: Hadoop HDFS
>          Issue Type: Test
>          Components: test
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>         Attachments: HDFS669.patch
> Most HDFS tests are functional tests that test a feature end to end by running a mini
cluster. We should add more tests like TestReplication that attempt to stress individual classes
in isolation, ie by stubbing out dependencies without running a mini cluster. This allows
for more fine-grain testing and making tests run much more quickly because they avoid the
cost of cluster setup and teardown. If it makes sense to use another framework besides junit
we should standardize with MAPREDUCE-1050. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message