hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6395) Assorted improvements to xattr limit checking
Date Tue, 10 Jun 2014 02:02:02 GMT

    [ https://issues.apache.org/jira/browse/HDFS-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026032#comment-14026032

Andrew Wang commented on HDFS-6395:

Woops, my bad, I forgot that this patch also fixes the # limit to not apply to the non-user
namespaces. I had a few comments:

- Would be nice to test that the system namespace isn't affected by these limits, I guess
reach into FSNamesystem or FSDirectory via @VisibleForTesting methods.
- Let's remove the prints when the limits hit their max, since I think that was a misunderstanding
of Chris' comment about printing.

Thanks Yi!

> 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

View raw message