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

Hudson commented on HDFS-7757:
------------------------------

SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2072 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2072/])
HDFS-7757. Misleading error messages in FSImage.java. (Contributed by Brahma 
Reddy Battula) (arp: rev 1004473aa612ee3703394943f25687aa5bef47ea)
* 
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSImage.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt


> Misleading error messages in FSImage.java
> -----------------------------------------
>
>                 Key: HDFS-7757
>                 URL: https://issues.apache.org/jira/browse/HDFS-7757
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>    Affects Versions: 2.6.0
>            Reporter: Arpit Agarwal
>            Assignee: Brahma Reddy Battula
>             Fix For: 2.7.0
>
>         Attachments: HDFS-7757-002.patch, HDFS-7757.patch
>
>
> If a quota violation is detected while loading an image, the NameNode logs 
> scary error messages indicating a bug. However the quota violation state is 
> very easy to get into e.g.
> # Copy a 2MB file to a directory.
> # Set a disk space quota of 1MB on the directory. We are in quota violation 
> state now.
> We should reword the error messages, ideally making them warnings and 
> suggesting the administrator needs to fix the quotas:
> Relevant code:
> {code}
>         LOG.error("BUG: Diskspace quota violation in image for "
>             + dir.getFullPathName()
>             + " quota = " + dsQuota + " < consumed = " + diskspace);
> ...
>           LOG.error("BUG Disk quota by storage type violation in image for "
>               + dir.getFullPathName()
>               + " type = " + t.toString() + " quota = "
>               + typeQuota + " < consumed " + typeSpace);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to