hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo Nicholas Sze (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6099) HDFS file system limits not enforced on renames.
Date Tue, 18 Mar 2014 21:22:44 GMT

    [ https://issues.apache.org/jira/browse/HDFS-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13939821#comment-13939821

Tsz Wo Nicholas Sze commented on HDFS-6099:

I still think that rename in the same dir should not throw exception since the rename does
not increase the usage.  Just like that we should allow setPermission if there is already
some violation in the fs limits.

For quota, I believe it allows rename under the same directory even if the quota is already

> HDFS file system limits not enforced on renames.
> ------------------------------------------------
>                 Key: HDFS-6099
>                 URL: https://issues.apache.org/jira/browse/HDFS-6099
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.3.0
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>             Fix For: 2.4.0
>         Attachments: HDFS-6099.1.patch, HDFS-6099.2.patch, HDFS-6099.3.patch
> {{dfs.namenode.fs-limits.max-component-length}} and {{dfs.namenode.fs-limits.max-directory-items}}
are not enforced on the destination path during rename operations.  This means that it's still
possible to create files that violate these limits.

This message was sent by Atlassian JIRA

View raw message