[
https://issues.apache.org/jira/browse/HDFS-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013399#comment-14013399
]
Yi Liu commented on HDFS-6395:
------------------------------
Hi [~andrew.wang], I think current implementation already covers what we want.
- XAttr enable/disable config flag and limits configs only affects
user-settable namespaces (i.e. user and trusted)
- System and security namespace have no limits, and are still available even if
xattrs are disabled
For XAttr enable/disable config flag and size limits configs, we check them in
{{FSNamesystem}} and RPC calls will be delegated to there. Only user-settable
namespaces (user and trusted) are allowed.
Internal HDFS features (in HDFS core) should use the methods ({{setXAttr}},
{{getXAttrs}}, {{removeXAttr}}) in {{FSdirectory}}, and there we don't check
the XAttr enable/disable config flag and size limits configs.
If you agree with this, we can close this JIRA as fixed?
> 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)
