hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhilei Xu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-6585) INodesInPath.resolve is called multiple times in FSNamesystem.setPermission
Date Sun, 22 Jun 2014 02:29:24 GMT

     [ https://issues.apache.org/jira/browse/HDFS-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Zhilei Xu updated HDFS-6585:

    Attachment: patch_f15b7d505f12213f1ee9fb5ddb4bdaa64f9f623d.txt

> INodesInPath.resolve is called multiple times in FSNamesystem.setPermission
> ---------------------------------------------------------------------------
>                 Key: HDFS-6585
>                 URL: https://issues.apache.org/jira/browse/HDFS-6585
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: Zhilei Xu
>            Assignee: Zhilei Xu
>              Labels: patch
>         Attachments: patch_ab60af58e03b323dd4b18d32c4def1f008b98822.txt, patch_f15b7d505f12213f1ee9fb5ddb4bdaa64f9f623d.txt
> Most of the APIs (both internal and external) in FSNamesystem calls INodesInPath.resolve()
to get the list of INodes corresponding to a file path. Usually one API will call resolve()
multiple times and that's a waste of time.
> This issue particularly refers to FSNamesystem.setPermission, which calls resolve() twice
indirectly: one from checkOwner(), another from dir.setPermission().
> Should save the result of resolve(), and use it whenever possible throughout the lifetime
of an API call, instead of making new resolve() calls.

This message was sent by Atlassian JIRA

View raw message