Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 5 Apr 2012 09:31:34 +0000 (UTC)
From: "madhukara phatak (Commented) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <260587427.16347.1333618294504.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1965905009.50221.1329473760839.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-2964) No notice in any logs if
 dfs.datanode.du.reserved is greater than available disk space
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

madhukara phatak commented on HDFS-2964:
----------------------------------------

This is just addition for log message so no need of test case.
                
> No notice in any logs if dfs.datanode.du.reserved is greater than available disk space
> --------------------------------------------------------------------------------------
>
>                 Key: HDFS-2964
>                 URL: https://issues.apache.org/jira/browse/HDFS-2964
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node, name-node
>    Affects Versions: 0.20.2
>            Reporter: Robert J Berger
>            Priority: Minor
>         Attachments: HDFS-2964-1.patch, HDFS-2964.patch
>
>
> We spent a long time tracking down why a test hdfs cluster seemed to be running fine, but would not allow the mapred system to come up complaining that "could only be replicated to 0 nodes, instead of 1".
> There were no namenode or datanode errors in any of the logs. hadoop fsck said everything was good. At first glance dfsadmin -report looked good. It wasn't until I realized that there was 0 Capacity available that we poked around and found https://groups.google.com/a/cloudera.org/group/scm-users/msg/a4252d6623adbc2d which mentioned that the "reserverd space" might be greater than the disk space available. And we did find that our dfs.datanode.du.reserved was indeed higher than our actual since we were only testing a small cluster.
> It seems that there should be some warning or error in the logs that say that.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira