[
https://issues.apache.org/jira/browse/HDFS-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617853#comment-13617853
]
Plamen Jeliazkov commented on HDFS-4639:
----------------------------------------
My results were 6 failed tests amd 1 error. The failures seem to be related to
symlinks.
I am unsure about the "testSaveNamespace" failure though -- I will look into
it; nor am I sure about the corrupt replicas.
Failed tests:
testCreateWithPartQualPathFails(org.apache.hadoop.fs.TestFcHdfsSymlink): HDFS
requires URIs with schemes have an authority
testCreateLinkUsingRelPaths(org.apache.hadoop.fs.TestFcHdfsSymlink)
testCreateLinkUsingAbsPaths(org.apache.hadoop.fs.TestFcHdfsSymlink)
testCreateLinkUsingFullyQualPaths(org.apache.hadoop.fs.TestFcHdfsSymlink)
testSaveNamespace(org.apache.hadoop.hdfs.server.namenode.TestCheckpoint):
File
/Users/plamenjeliazkov/Documents/workspace/hadoop-common/hadoop-hdfs-project/hadoop-hdfs/target/test/data/dfs/name1/current/edits_0000000000000000001-0000000000000000012
should exist
Tests in error:
testCorruptBlockRereplicatedAcrossRacks(org.apache.hadoop.hdfs.server.blockmanagement.TestBlocksWithNotEnoughRacks):
Timed out waiting for corrupt replicas. Waiting for 1, but only found 0
> startFileInternal() should not increment generation stamp
> ---------------------------------------------------------
>
> Key: HDFS-4639
> URL: https://issues.apache.org/jira/browse/HDFS-4639
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.0.3-alpha
> Reporter: Konstantin Shvachko
> Assignee: Plamen Jeliazkov
> Attachments: HDFS-4639.patch
>
>
> startFileInternal() increments genStamp and passes it to
> FSDirectory.addFile() as a parameter, while the addFile() simply ignores the
> generationStamp parameter.
> We should remove the call of nextGenerationStamp() in startFileInternal() and
> eliminate the redundant parameter in FSDirectory.addFile().
--
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
