[
https://issues.apache.org/jira/browse/HDFS-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019687#comment-14019687
]
Yi Liu commented on HDFS-6395:
------------------------------
Thanks Andrew.
When I look into the detail and discussed with Uma, we found some issue.
We need to get the full inode path for printing, it a bit different to get the
full inode path when loading an inode.
The fsimage protobuf serialization is as following:
{code}
saver.serializeINodeSection(sectionOutputStream);
saver.serializeINodeDirectorySection(sectionOutputStream);
saver.serializeFilesUCSection(sectionOutputStream);
{code}
So we can't get the inodes map when loading inode section. We can't simply
change the order and it doesn't work.
An alternative way is only print the current inode name (not including the
parents) and the inode id, but I think the user/admin will not know what an
inode id is.
Thoughts?
> Assorted improvements to xattr limit checking
> ---------------------------------------------
>
> Key: HDFS-6395
> URL: https://issues.apache.org/jira/browse/HDFS-6395
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.0.0
> Reporter: Andrew Wang
> Assignee: Yi Liu
> Attachments: HDFS-6395.patch
>
>
> It'd be nice to print messages during fsimage and editlog loading if we hit
> either the # of xattrs per inode or the xattr size limits.
> We should also consider making the # of xattrs limit only apply to the user
> namespace, or to each namespace separately, to prevent users from locking out
> access to other namespaces.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
