Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9F249C27C for ; Fri, 5 Dec 2014 22:24:13 +0000 (UTC) Received: (qmail 62694 invoked by uid 500); 5 Dec 2014 22:24:13 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 62556 invoked by uid 500); 5 Dec 2014 22:24:13 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 62538 invoked by uid 99); 5 Dec 2014 22:24:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Dec 2014 22:24:13 +0000 Date: Fri, 5 Dec 2014 22:24:13 +0000 (UTC) From: "Jing Zhao (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-7474) Avoid resolving path in FSPermissionChecker MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-7474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-7474: ---------------------------- Resolution: Fixed Fix Version/s: 2.7.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) I've committed this to trunk and branch-2. Thanks Haohui for the review! > Avoid resolving path in FSPermissionChecker > ------------------------------------------- > > Key: HDFS-7474 > URL: https://issues.apache.org/jira/browse/HDFS-7474 > Project: Hadoop HDFS > Issue Type: Improvement > Components: namenode > Reporter: Jing Zhao > Assignee: Jing Zhao > Fix For: 2.7.0 > > Attachments: HDFS-7474.000.patch, HDFS-7474.001.patch > > > Currently for an typical namenode operation a path can be resolved multiple times. Usually the FSPermissionChecker first takes the path string as input and resolve the path before the real checking. After permission checking the path is then resolved again (and again) for real operations in FSNamesystem and FSDirectory. Ideally we should resolve the path only once, and use INodesInPath internally afterwards. As a first step, we can start from avoiding path resolving in FSPermissionChecker. -- This message was sent by Atlassian JIRA (v6.3.4#6332)