[
https://issues.apache.org/jira/browse/HDFS-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628943#comment-13628943
]
Daryn Sharp commented on HDFS-4434:
-----------------------------------
bq. Suggestion - given that you are reserving 10 bits why not go a little
further and reserve 14bits – don't have any use cases right now.
I'm curious what the theorized need is for reserved inode numbers? It seems
that by trying to account for entirely unknown features, we are adding a
restriction that may not be correct and/or sufficient.
I'd suggest using 0 for the root inode, and if in the future we need to
identify other "special" inodes that we use something akin to a traditional
superblock (not to be confused with hdfs blocks), or metadata on inodes, to
reference other "special" inodes. That would be flexible w/o artificial
limitations.
> 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: Suresh Srinivas
> Attachments: HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch,
> HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch,
> HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch,
> HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch, HDFS-4434.patch,
> HDFS-4434.patch, HDFS-4434.patch
>
>
> 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
