[
https://issues.apache.org/jira/browse/HDFS-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14014642#comment-14014642
]
Yi Liu commented on HDFS-6395:
------------------------------
Thanks [~andrew.wang]. Right, I will remove the unnecessary import.
I change the {{dfs.namenode.fs-limits.max-xattrs-per-inode}} only affects
user-settable namespaces too. Now for xattrs, user's behavior will not affect
internal HDFS features at all.
For printing message when things exceed limits. I add the log in {{setXAttr}}
and maybe it's better than log during fsimage and editlog loading, it's easier
to get all xattrs of inode there and only user-settable namspaces have the
limit.
> 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
>
> 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)
