Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 19 Jan 2016 18:11:39 +0000 (UTC)
From: "Kihwal Lee (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12856202.1439569228000.149909.1453227099909@Atlassian.JIRA>
In-Reply-To: <JIRA.12856202.1439569228000@Atlassian.JIRA>
References: <JIRA.12856202.1439569228000@Atlassian.JIRA>
 <JIRA.12856202.1439569228970@arcas>
Subject: [jira] [Commented] (HDFS-8898) Create API and command-line argument
 to get quota and quota usage without detailed content summary
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kihwal Lee commented on HDFS-8898:
----------------------------------

How does a new client work with an older namenode that does not implement getQuotaUsage?
If we are not planning on making it work, we should probably show more user friendly error message.
Other than that the patch looks good. Also it still applies!

> Create API and command-line argument to get quota and quota usage without detailed content summary
> --------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-8898
>                 URL: https://issues.apache.org/jira/browse/HDFS-8898
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: fs
>            Reporter: Joep Rottinghuis
>            Assignee: Ming Ma
>         Attachments: HDFS-8898-2.patch, HDFS-8898-3.patch, HDFS-8898-4.patch, HDFS-8898.patch
>
>
> On large directory structures it takes significant time to iterate through the file and directory counts recursively to get a complete ContentSummary.
> When you want to just check for the quota on a higher level directory it would be good to have an option to skip the file and directory counts.
> Moreover, currently one can only check the quota if you have access to all the directories underneath. For example, if I have a large home directory under /user/joep and I host some files for another user in a sub-directory, the moment they create an unreadable sub-directory under my home I can no longer check what my quota is. Understood that I cannot check the current file counts unless I can iterate through all the usage, but for administrative purposes it is nice to be able to get the current quota setting on a directory without the need to iterate through and run into permission issues on sub-directories.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)