Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 22 Mar 2011 05:03:05 +0000 (UTC)
From: "Robert Chansler (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <699219021.3245.1300770185721.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1024545672.871.1300114349811.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-1751) Intrinsic limits for HDFS files,
 directories
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HDFS-1751?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13009=
552#comment-13009552 ]=20

Robert Chansler commented on HDFS-1751:
---------------------------------------

First, I must =E2=80=98fess up that =E2=80=9Cintrinsic=E2=80=9D was my sugg=
estion. I understand Jakob=E2=80=99s point, but defend my choice as well re=
presenting the intention that the limit be independent of any particular di=
rectory or user. The whole point is avoid exhausting resources by foolish/m=
istaken activity. And quota is a resource, which is why this facility needs=
 to be independent. Testing the limits (=E2=80=9Cintrinsic=E2=80=9D or othe=
rwise) at the same place as the quotas are tested make sense as the same lo=
gic applies if the test fails. (The information returned to the client shou=
ld distinguish the faults.) But the intent would be defeated if there were =
anything like per-directory configuration. Not to mention that the implemen=
tation would be more complex, extra space would be consumed, and the comple=
xity presented to users and administrators would be increased.=20

> 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-3.patch, HDFS-1751-4.pa=
tch, 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 g=
ood reasons for those kinds of limits, but that is not the intended scope o=
f this feature. Consequently, a reasonable implementation might be to exten=
d 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 prob=
lem 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