hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-4749) Use INodeId to identify the corresponding directory node for FSImage saving/loading
Date Thu, 25 Apr 2013 18:44:15 GMT

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

Tsz Wo (Nicholas), SZE updated HDFS-4749:
-----------------------------------------

     Component/s:     (was: datanode)
    Hadoop Flags: Reviewed

+1 patch looks good.  This cleans up a lot of code.
                
> Use INodeId to identify the corresponding directory node for FSImage saving/loading
> -----------------------------------------------------------------------------------
>
>                 Key: HDFS-4749
>                 URL: https://issues.apache.org/jira/browse/HDFS-4749
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>         Attachments: HDFS-4749.000.patch
>
>
> Currently in fsimage, we use the path to locate a directory node for later loading, i.e.,
when loading a subtree from fsimage, we first read the path of the directory node, and resolve
the path to identify the directory node. This brings extra complexity since we need to generate
path for directory nodes in both the current tree and snapshot copies.
> As a simplification, we can use INodeId to identify the directory node.

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