[
https://issues.apache.org/jira/browse/HDFS-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995494#comment-13995494
]
Daryn Sharp commented on HDFS-6326:
-----------------------------------
bq. failing to justify the performance concerns leads Chris and I to decide to
keep ACL out of the critical path, and to move the complexity to ls / web UI.
Performance concern: The additional rpc and/or http calls. I misspoke when I
had 2X the calls. It's 1 listStatus per directory, N-many getAclStatus per
item just to decide whether to print a "+" or a " ". Let's take a real world
example from a busy cluster: 200ms queue time, 2ms response time. Listing a
directory with 100 items will take an extra ~20s. Listing 1000 items will take
an extra ~3.4m. We have users that ls larger datasets.
This is unacceptable.
> WebHdfs ACL compatibility is broken
> -----------------------------------
>
> Key: HDFS-6326
> URL: https://issues.apache.org/jira/browse/HDFS-6326
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
> Affects Versions: 3.0.0, 2.4.0
> Reporter: Daryn Sharp
> Assignee: Chris Nauroth
> Priority: Blocker
> Attachments: HDFS-6326.1.patch, HDFS-6326.2.patch, HDFS-6326.3.patch
>
>
> 2.4 ACL support is completely incompatible with <2.4 webhdfs servers. The NN
> throws an {{IllegalArgumentException}} exception.
> {code}
> hadoop fs -ls webhdfs://nn/
> Found 21 items
> ls: Invalid value for webhdfs parameter "op": No enum constant
> org.apache.hadoop.hdfs.web.resources.GetOpParam.Op.GETACLSTATUS
> [... 20 more times...]
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
