Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 4 Jun 2012 20:38:23 +0000 (UTC)
From: "Aaron T. Myers (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <672607608.36110.1338842303410.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1927474368.35384.1338832944519.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HADOOP-8479) update HDFS quotas guide:
 currently says setting quota fails if the directory would be in violation
 of the new quota
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aaron T. Myers commented on HADOOP-8479:
----------------------------------------

I'm happy to be convinced otherwise, but presently I'm of the opinion that this seems like an error in the docs. Setting a quota is an administrative command, so if an administrator notices a user directory that's using too much space, they might want to set a quota on it which would then force the user to later clean up that dir as they see fit. I don't think the administrator should be required to clean up the dir before being able to set the quota.
                
> update HDFS quotas guide: currently says setting quota fails if the directory would be in violation of the new quota
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8479
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8479
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Stephen Chu
>              Labels: newbie
>
> http://hadoop.apache.org/common/docs/r0.20.0/hdfs_quota_admin_guide.html
> The guide says "The attempt to set a quota fails if the directory would be in violation of the new quota" for both Name Quotas and Space Quotas.
> That doesn't seem to be the case, though. I can set the quota successfully even when the directory violates the new quota.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira