[
https://issues.apache.org/jira/browse/HDFS-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019500#comment-14019500
]
Andrew Wang commented on HDFS-6395:
-----------------------------------
I chatted with Yi a bit offline with some review feedback, re-posting here:
I think the idea with the printing was a situation where the admin lowers the
xattr limits and restarts the NN. It'd be nice to print out a message if the NN
encounters any XAttrs that exceed the new lower limit during metadata loading.
Doing this precisely is some work (the edit log might add then remove xattrs,
bringing it back under the limit), but I think the rough solution of just
printing whenever a limit is exceeded is good enough.
> 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)
