hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Boris Shkolnik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5862) Namespace quota exceeded message unclear
Date Thu, 18 Jun 2009 20:44:07 GMT

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

Boris Shkolnik commented on HADOOP-5862:
----------------------------------------

   [exec] /home/sureshms/tools/buildtools/ant/apache-ant-1.7.1/bin/ant -Dversion=PATCH-HADOOP-5862-1.patch
-Djava5.home=/usr/releng/tools/java/jdk1.5.0_06 -Dforrest.home=/home/ndaley/tools/forrest/latest
-DHadoopPatchProcess= releaseaudit > ../scratch_dir//patchReleaseAuditWarnings.txt 2>&1
     [exec] 
     [exec] 
     [exec] There appear to be 499 release audit warnings before the patch and 499 release
audit warnings after applying the patch.
     [exec] 
     [exec] 
     [exec] 
     [exec] 
     [exec] +1 overall.  
     [exec] 
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec] 
     [exec]     +1 tests included.  The patch appears to include 14 new or modified tests.
     [exec] 
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
     [exec] 
     [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler
warnings.
     [exec] 
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs warnings.
     [exec] 
     [exec]     +1 Eclipse classpath. The patch retains Eclipse classpath integrity.
     [exec] 
     [exec]     +1 release audit.  The applied patch does not increase the total number of
release audit warnings.
     [exec] 
     [exec] 
     [exec] 
     [exec] 


> Namespace quota exceeded message unclear
> ----------------------------------------
>
>                 Key: HADOOP-5862
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5862
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>            Reporter: eric baldeschwieler
>            Assignee: Boris Shkolnik
>         Attachments: HADOOP-5862-1.patch, HADOOP-5862.patch, HADOOP-5862.patch, HADOOP-5862.patch,
HADOOP-5862.patch
>
>
> We seem to return one generic message when either a namespace or diskspace quota is exceeded.
 We should be clearer.   The error should state which quota is exceeded and only report statistics
on the exceeded quota.
> Further namespace quota is probably not clear to most users.  We should probably have
explanatory text such as: "you have exceeded the maximum allowed number of files".  Maybe
we should even rename the quota to number of files quota?
> Finally, the error below would be clearer if it read:
>   Quota exceeded for directory '/user/ciyaliao'.
> By not using the word "directory" it is not clear in this case if the issue is with a
user or a directory.
> ------ AN EXAMPLE -----
> > Hi, 
> > 
> > I encountered an error:
> > 
> > put: org.apache.hadoop.hdfs.protocol.QuotaExceededException: The quota of
> > /user/x is exceeded: namespace quota=200000 file count=200001,
> > diskspace quota=-1 diskspace=-44221467605496
> > 
> > It apparently complains that dfs quota is exceeded. But I only use around
> > 200GB disk space. From the error message, what kind of quota did I actually
> > exceed? How do I check my usage of this type of quota?
> > 
> > Thanks,
> > x

-- 
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