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 Fri, 30 May 2014 20:17:01 GMT

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

Andrew Wang commented on HDFS-6395:
-----------------------------------

Makes sense to me, thanks for investigating Yi. We should still fix up Chris's earlier comments
from a prior review though, which were printing messages during metadata loading when things
exceed limits, and removing the unnecessary import.

> 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)

Mime
View raw message