hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pete Wyckoff (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3938) Quotas for disk space management
Date Tue, 16 Sep 2008 00:49:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631220#action_12631220
] 

Pete Wyckoff commented on HADOOP-3938:
--------------------------------------

>From the user spec:

"Quotas are persistent with the fsimage. When starting, if the fsimage is immediately in violation
of a quota (perhaps the fsimage was surreptitiously modified), the startup operation fails
with an error report"

So, how as an administrator could I ever fix such a problem? Are there administration commands
that are going to work directly on the fsimage without a namenode?  This seems like a very
poor requirement.




> 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, HADOOP-3938.patch, HADOOP-3938.patch, HADOOP-3938.patch,
HADOOP-3938.patch, 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.


Mime
View raw message