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 7245217571 for ; Mon, 27 Oct 2014 07:36:35 +0000 (UTC) Received: (qmail 1554 invoked by uid 500); 27 Oct 2014 07:36:34 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 1472 invoked by uid 500); 27 Oct 2014 07:36:34 -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 1309 invoked by uid 99); 27 Oct 2014 07:36:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Oct 2014 07:36:34 +0000 Date: Mon, 27 Oct 2014 07:36:34 +0000 (UTC) From: "Harsh J (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (HDFS-7292) Improve error messages for checkOwner permission related failures 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-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J reassigned HDFS-7292: ----------------------------- Assignee: Harsh J > Improve error messages for checkOwner permission related failures > ----------------------------------------------------------------- > > Key: HDFS-7292 > URL: https://issues.apache.org/jira/browse/HDFS-7292 > Project: Hadoop HDFS > Issue Type: Improvement > Components: namenode > Affects Versions: 2.2.0 > Reporter: Harsh J > Assignee: Harsh J > Priority: Trivial > Attachments: HDFS-7292.patch > > > If a bad file create request fails, you get a juicy error self-describing the reason almost: > {code}Caused by: org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException): Permission denied: user=root, access=WRITE, inode="/":hdfs:supergroup:drwxr-xr-x{code} > However, if a setPermission fails, one only gets a vague: > {code}Caused by: org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException): Permission denied{code} > It would be nicer if all forms of permission failures logged the accessed inode and current ownership and permissions in the same way. -- This message was sent by Atlassian JIRA (v6.3.4#6332)