[
https://issues.apache.org/jira/browse/HDFS-6765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077708#comment-14077708
]
Daryn Sharp commented on HDFS-6765:
-----------------------------------
Other than the inconsistency with other edit ops, is this going to break
compatibility for the edits viewer?
I'm a bit leery due to recent edit log corruptions. Replaying the edit based
on inode instead of path isn't replaying the edit as originally issued which
may mask edit bugs.
I'll look at HDFS-6757 but could you elaborate on what impact this has on
performance (other than re-building the path?) and what cleanup it blocks?
> Log INodeID instead of full path in edit log when closing a file
> ----------------------------------------------------------------
>
> Key: HDFS-6765
> URL: https://issues.apache.org/jira/browse/HDFS-6765
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Haohui Mai
>
> When closing a file, currently the edit log records the full path instead of
> the inode id. The performance is sub-optimal, and it prevents further clean
> ups of the code (e.g., HDFS-6757)
> This jira proposes to record inode id instead of the full path in edit logs
> when closing a file.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
