[
https://issues.apache.org/jira/browse/HADOOP-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Chansler updated HADOOP-3187:
------------------------------------
Release Note: Introduced directory quota as hard limits on the number of
names in the tree rooted at that directory. An administrator may set quotas on
individual directories explicitly. Newly created directories have no associated
quota. File/directory creations fault if the quota would be exceeded. The
attempt to set a quota faults if the directory would be in violation of the new
quota. (was: The directory quota is a hard limit on the number of names in
the tree rooted at that directory. This jira allows an administrator to set
quotas on individual directories explicitly. Newly created directories have no
associated quota. The largest quota is Long.Max_Value. A quota of one forces a
directory to remain empty. File/directory creations fault if the quota would
be exceeded. Quotas stick to renamed directories; the rename operation
faults if operation would result in a quota violation. The attempt to set a
quota faults if the directory would be in violation of the new quota. )
> Quotas for name space management
> --------------------------------
>
> Key: HADOOP-3187
> URL: https://issues.apache.org/jira/browse/HADOOP-3187
> Project: Hadoop Core
> Issue Type: New Feature
> Reporter: Robert Chansler
> Assignee: Hairong Kuang
> Fix For: 0.18.0
>
> Attachments: quota.patch, quota1.patch, quota2.patch, quota3.patch,
> quota4.patch, QuotasDesign.pdf, QuotasDesign1.pdf, QuotasDesign2.pdf
>
>
> Create a quota mechanism for name space management.
> Quota set at a directory by super user restricts that number of names in and
> below that directory.
> Quota tested by create() and rename().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
