hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-4927) CreateEditsLog creates inodes with an invalid inode ID, which then cannot be loaded by a namenode.
Date Mon, 24 Jun 2013 23:20:20 GMT

     [ https://issues.apache.org/jira/browse/HDFS-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Nauroth updated HDFS-4927:
--------------------------------

    Attachment: HDFS-4927.1.patch

Here is a patch that fixes the bug by generating valid inode IDs.  I also added a test that
validates an edits file created with this tool can then be loaded by a namenode.
                
> 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
>            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