hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4434) Provide a mapping from INodeId to INode
Date Thu, 24 Jan 2013 18:17:13 GMT

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

Aaron T. Myers commented on HDFS-4434:

I think Colin's point is that if the goal is to error out when a client's INode ID doesn't
match what's in the NN's leases, then there's no need for a map from INode ID to INode. We
need only note that the INode IDs don't match and throw an error.

My understanding of the design/goals is based on [this comment|https://issues.apache.org/jira/browse/HDFS-4258?focusedCommentId=13537283&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13537283]
made by Brandon. If the goals are more than this, I'd really like to see a little design doc
for this work.
> Provide a mapping from INodeId to INode
> ---------------------------------------
>                 Key: HDFS-4434
>                 URL: https://issues.apache.org/jira/browse/HDFS-4434
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>    Affects Versions: 3.0.0
>            Reporter: Brandon Li
>            Assignee: Brandon Li
> This JIRA is to provide a way to access the INode via its id. The proposed solution is
to have an in-memory mapping from INodeId to INode. 

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

View raw message