You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Jing Zhao (JIRA)" <ji...@apache.org> on 2013/05/28 04:55:20 UTC

[jira] [Updated] (HDFS-4857) Snapshot.Root and AbstractINodeDiff#snapshotINode should not be put into INodeMap when loading FSImage

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

Jing Zhao updated HDFS-4857:
----------------------------

    Attachment: HDFS-4857.001.patch

Initial patch to fix the bug.
                
> Snapshot.Root and AbstractINodeDiff#snapshotINode should not be put into INodeMap when loading FSImage
> ------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-4857
>                 URL: https://issues.apache.org/jira/browse/HDFS-4857
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>         Attachments: HDFS-4857.001.patch
>
>
> Snapshot.Root, though is a subclass of INodeDirectory, is only used to indicate the root of a snapshot. In the meanwhile, AbstractINodeDiff#snapshotINode is used as copies recording the original state of an INode. Thus we should not put them into INodeMap. 
> Currently when loading FSImage we did not check the type of inode and wrongly put these two types of nodes into INodeMap. This may replace the nodes that should stay in INodeMap.

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