[
https://issues.apache.org/jira/browse/HADOOP-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625811#action_12625811
]
Raghu Angadi commented on HADOOP-3938:
--------------------------------------
bq. Somewhat more subtle than R's comment, it would not be possible to create a
file in a directory with zero quota as creation requires that a block's-worth
of quota is available. But one might think of setting a zero quota on a
directory with only zero-length files.
Actually creating a file does not require block allocations. So space quota
will be not be checked. It is possible to do {{dfs.create(); dfs.close()}},
even in a directory that reached its space quota. Is that what we want?
> Also, did you want to include the updated documentation in this patch?
sure, but not required in this jira.
Irrespective of whether it is possible or not, I think we need clarify/decide
the policy : Should creating an empty file take up any space quota?
> Quotas for disk space management
> --------------------------------
>
> Key: HADOOP-3938
> URL: https://issues.apache.org/jira/browse/HADOOP-3938
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Reporter: Robert Chansler
> Assignee: Raghu Angadi
> Fix For: 0.19.0
>
> Attachments: HADOOP-3938.patch, hdfs_quota_admin_guide.pdf,
> hdfs_quota_admin_guide.xml
>
>
> Directory quotas for bytes limit the number of bytes used by files in and
> below the directory. Operation is independent of name quotas (HADOOP-3187),
> but the implementation is parallel. Each file is charged according to its
> length multiplied by its intended replication factor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
