[
https://issues.apache.org/jira/browse/HDFS-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007068#comment-13007068
]
Jakob Homan commented on HDFS-1751:
-----------------------------------
bq. As far as I can tell, there is an existing quota for all the items in the
entire tree beneath a directory, but this is a quota for the number of allowed
items in each specific directory in the filesystem. Ie. you may have a current
quota of 15 items for a directory tree, but the new quota only allows each
directory to have 5 items.
I share Boris' concern over this. This feature seems like a refinement to the
namespace quota, but is being implemented completely separately from it. This
may well lead to confusion on the users' part and annoyance for Ops. Let's
discuss this further before this is committed.
> Intrinsic limits for HDFS files, directories
> --------------------------------------------
>
> Key: HDFS-1751
> URL: https://issues.apache.org/jira/browse/HDFS-1751
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: data-node
> Affects Versions: 0.22.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Fix For: 0.23.0
>
> Attachments: HDFS-1751-2.patch, HDFS-1751.patch
>
>
> Enforce a configurable limit on:
> the length of a path component
> the number of names in a directory
> The intention is to prevent a too-long name or a too-full directory. This is
> not about RPC buffers, the length of command lines, etc. There may be good
> reasons for those kinds of limits, but that is not the intended scope of this
> feature. Consequently, a reasonable implementation might be to extend the
> existing quota checker so that it faults the creation of a name that violates
> the limits. This strategy of faulting new creation evades the problem of
> existing names or directories that violate the limits.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
