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] [Commented] (HDFS-4334) Add a unique id to each INode
Date Fri, 28 Dec 2012 08:20:17 GMT

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

Tsz Wo (Nicholas), SZE commented on HDFS-4334:
----------------------------------------------

+1 patch looks good.

> ... The INodeId code is practically identical to GenerationStamp class modular some members
rename. ...

I feel the same way.  Just have filed HDFS-4346 to do the refactoring.
                
> Add a unique id to each INode
> -----------------------------
>
>                 Key: HDFS-4334
>                 URL: https://issues.apache.org/jira/browse/HDFS-4334
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Brandon Li
>            Assignee: Brandon Li
>         Attachments: HDFS-4334.patch, HDFS-4334.patch, HDFS-4334.patch
>
>
> This JIRA is to track the task to add inode id, which is a 64bit number. 
> Unlike many local file systems, HDFS doesn't recycle 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