hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhe Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-10673) Optimize FSPermissionChecker's internal path usage
Date Mon, 12 Sep 2016 23:13:21 GMT

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

Zhe Zhang commented on HDFS-10673:

Verified all reported failures pass locally. Pushed to branch-2.7.

> Optimize FSPermissionChecker's internal path usage
> --------------------------------------------------
>                 Key: HDFS-10673
>                 URL: https://issues.apache.org/jira/browse/HDFS-10673
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>             Fix For: 2.8.0, 2.9.0, 2.7.4, 3.0.0-alpha1
>         Attachments: HDFS-10673-branch-2.7.00.patch, HDFS-10673.1.patch, HDFS-10673.2.patch,
> The INodeAttributeProvider and AccessControlEnforcer features degrade performance and
generate excessive garbage even when neither is used.  Main issues:
> # A byte[][] of components is unnecessarily created.  Each path component lookup converts
a subrange of the byte[][] to a new String[] - then not used by default attribute provider.
> # Subaccess checks are insanely expensive.  The full path of every subdir is created
by walking up the inode tree, creating a INode[], building a string by converting each inode's
byte[] name to a string, etc.  Which will only be used if there's an exception.
> The expensive of #1 should only be incurred when using the provider/enforcer feature.
 For #2, paths should be created on-demand for exceptions.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message