[
https://issues.apache.org/jira/browse/HDFS-15248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071650#comment-17071650
]
Stephen O'Donnell commented on HDFS-15248:
------------------------------------------
This has come up before in HDFS-7447 and we opted not to make this configurable.
While your cluster will use this feature sparingly, my fear is that if we open
it up to be configurable some people will abuse the feature and create problems
for themselves, and for those of us who support the clusters.
Reading the comment in HDFS-7447, it seems that other ext based file systems
have a 32 ACL limit too, so in that respect we are consisted with them.
The usual answer to this sort of problem is that either:
1) Use Sentry a or Ranger type plugin
2) Rather than adding lots of users to an ACL, create a group for access to the
directory and assign that group to the users at the unix group / Active
Directory level which is probably more flexible and less error prone.
> Make the maximum number of ACLs entries configurable
> ----------------------------------------------------
>
> Key: HDFS-15248
> URL: https://issues.apache.org/jira/browse/HDFS-15248
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Reporter: Yang Yun
> Assignee: Yang Yun
> Priority: Minor
> Attachments: HDFS-15248.001.patch, HDFS-15248.002.patch,
> HDFS-15248.patch
>
>
> For big cluster, the hardcode 32 of ACLs maximum number is not enough, make
> it configurable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
