[
https://issues.apache.org/jira/browse/HDFS-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628050#comment-13628050
]
Suresh Srinivas commented on HDFS-4489:
---------------------------------------
bq. Perhaps ASN.1 encoding the long for the inode id will significantly
decrease the memory consumption?
Can you add more details on how this would decrease memory consumption? BTW
inodeID was added as a part of HDFS-4334. See the discussion about how reduce
the impact of adding inode ID -
https://issues.apache.org/jira/browse/HDFS-4258?focusedCommentId=13508432&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13508432.
But I am not sure if that optimization is necessary at the expense of code.
Thoughts?
> Use InodeID as as an identifier of a file in HDFS protocols and APIs
> --------------------------------------------------------------------
>
> Key: HDFS-4489
> URL: https://issues.apache.org/jira/browse/HDFS-4489
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Reporter: Brandon Li
> Assignee: Brandon Li
>
> The benefit of using InodeID to uniquely identify a file can be multiple
> folds. Here are a few of them:
> 1. uniquely identify a file cross rename, related JIRAs include HDFS-4258,
> HDFS-4437.
> 2. modification checks in tools like distcp. Since a file could have been
> replaced or renamed to, the file name and size combination is no t reliable,
> but the combination of file id and size is unique.
> 3. id based protocol support (e.g., NFS)
> 4. to make the pluggable block placement policy use fileid instead of
> filename (HDFS-385).
--
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
