[
https://issues.apache.org/jira/browse/HDFS-7582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537671#comment-14537671
]
Vinayakumar B edited comment on HDFS-7582 at 5/11/15 7:05 AM:
--------------------------------------------------------------
bq. It would be great if we could find a definitive source that defines the
limit, but I haven't found it yet.
http://users.suse.com/~agruen/acl/linux-acls/online/#tab:acl_entries
I have tested on XFS, so I found the limit of 25 mentioned here for XFS. But
doc didnt say that its separately applied on access and default. Anyway this
limit was based on underlying FS implementations, Some supports in limiting #
of entries, some support limiting overall size.
In my earlier options, the option #1 (Apply the EXISTING limit (32) separately
on ACCESS and DEFAULT) was without backward incompatibility for existing
deployments. Of-course it increases the NN memory if extensively used.
What you say about option #1?
bq. Do you still want to consider changing this for 3.x? We'd have the
flexibility to make a backwards-incompatible change there.
I dont think so.
was (Author: vinayrpet):
bq. It would be great if we could find a definitive source that defines the
limit, but I haven't found it yet.
http://users.suse.com/~agruen/acl/linux-acls/online/#tab:acl_entries
I have tested on XFS, so I found the limit of 25 mentioned here for XFS. But it
didnt say that its separately applied on access and default. Anyway this limit
was based on inderlying FS implementations, Some supports in limiting # of
entries, some support limiting overall size.
In my earlier options, the option #1 (Apply the EXISTING limit (32) separately
on ACCESS and DEFAULT) was without backward incompatibility for existing
deployments. Of-course it increases the NN memory if extensively used.
What you say about option #1?
bq. Do you still want to consider changing this for 3.x? We'd have the
flexibility to make a backwards-incompatible change there.
I dont think so.
> Limit the number of default ACL entries to Half of maximum entries (16)
> -----------------------------------------------------------------------
>
> Key: HDFS-7582
> URL: https://issues.apache.org/jira/browse/HDFS-7582
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Reporter: Vinayakumar B
> Assignee: Vinayakumar B
> Attachments: HDFS-7582-001.patch
>
>
> Current ACL limits are only on the total number of entries.
> But there can be a situation where number of default entries for a directory
> will be more than half of the maximum entries, i.e. > 16.
> In such case, under this parent directory only files can be created which
> will have ACLs inherited using parent's default entries.
> But when directories are created, total number of entries will be more than
> the maximum allowed, because sub-directories copies both inherited ACLs as
> well as default entries.
> Since currently there is no check while copying ACLs from default ACLs
> directory creation succeeds, but any modification (only permission on one
> entry also) on the same ACL will fail.
> So it would be better to restrict the default entries to 16.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
