[
https://issues.apache.org/jira/browse/HADOOP-5862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720134#action_12720134
]
Hadoop QA commented on HADOOP-5862:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12410042/HADOOP-5862.patch
against trunk revision 785065.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 14 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
-1 release audit. The applied patch generated 495 release audit warnings
(more than the trunk's current 494 warnings).
-1 core tests. The patch failed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/504/testReport/
Release audit warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/504/artifact/trunk/patchprocess/releaseAuditDiffWarnings.txt
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/504/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/504/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/504/console
This message is automatically generated.
> 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.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.
