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 Mon, 09 Jun 2014 22:23:05 GMT

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

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

I should have realized this earlier, considering I worked on something pretty similar with
the fs-limits and the edit log before. I agree that it's difficult to do this without some
serious code gymnastics, so let's just table the entire thing for now. Please resolve this
if you agree, thanks again [~hitliuyi].

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

Mime
View raw message