hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4694) The SecondaryNameNode may change the inode id of root while doing checkpoint
Date Mon, 15 Apr 2013 03:16:19 GMT

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

Suresh Srinivas commented on HDFS-4694:
---------------------------------------

Jing, would this be an issue with HDFS-4434 which uses the same root inodeid always?
                
> The SecondaryNameNode may change the inode id of root while doing checkpoint
> ----------------------------------------------------------------------------
>
>                 Key: HDFS-4694
>                 URL: https://issues.apache.org/jira/browse/HDFS-4694
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>    Affects Versions: 3.0.0
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>         Attachments: HDFS-4694.001.patch
>
>
> SNN will call FSNamesystem#clear while merging the fsimage to its local FSNamesystem,
and the FSDirectory will be reset in this process. However, in FSDirectory#reset, a new inode
id will be allocated and assigned to the new root.
> To fix the problem, we can either pass in an inode id in FSDirectory#createRoot, or update
the root id in FSImageFormat#updateRootAttr.

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