hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4927) CreateEditsLog creates inodes with an invalid inode ID, which then cannot be loaded by a namenode.
Date Tue, 25 Jun 2013 13:12:21 GMT

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

Hudson commented on HDFS-4927:
------------------------------

Integrated in Hadoop-Hdfs-trunk #1441 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1441/])
    HDFS-4927. CreateEditsLog creates inodes with an invalid inode ID, which then cannot be
loaded by a namenode. Contributed by Chris Nauroth. (Revision 1496350)

     Result = FAILURE
cnauroth : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1496350
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/CreateEditsLog.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestCreateEditsLog.java

                
> CreateEditsLog creates inodes with an invalid inode ID, which then cannot be loaded by
a namenode.
> --------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-4927
>                 URL: https://issues.apache.org/jira/browse/HDFS-4927
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 3.0.0, 2.1.0-beta
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Minor
>         Attachments: HDFS-4927.1.patch
>
>
> {{CreateEditsLog#addFiles}} always creates inodes with ID hard-coded to {{INodeId#GRANDFATHER_INODE_ID}}.
 At initialization time, namenode will not load the resulting edits, because this is an invalid
inode ID.

--
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

Mime
View raw message