hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4021) Misleading error message when resources are low on the NameNode
Date Wed, 10 Oct 2012 00:00:03 GMT

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

Hadoop QA commented on HDFS-4021:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12548477/HDFS-4021.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-hdfs-project/hadoop-hdfs.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/3296//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3296//console

This message is automatically generated.
                
> Misleading error message when resources are low on the NameNode
> ---------------------------------------------------------------
>
>                 Key: HDFS-4021
>                 URL: https://issues.apache.org/jira/browse/HDFS-4021
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 2.0.3-alpha
>            Reporter: Colin Patrick McCabe
>            Priority: Minor
>              Labels: newbie
>         Attachments: HDFS-4021.patch
>
>
> When resources are low on the namenode, it enters SafeMode with a message like this:
> {code}
> 14:00:10,666  WARN NameNodeResourceChecker:89 - Space available on
> volume '/dev/hda1' is 104357888, which is below the configured
> reserved amount 104857600
> 14:00:10,670  WARN FSNamesystem:3190 - NameNode low on available disk
> space. Entering safe mode.
> 14:00:10,670  INFO StateChange:3836 - STATE* Safe mode is ON.
> Resources are low on NN. Safe mode must be turned off manually.
> {code}
> However, turning off safe mode manually has no effect, since it immediately puts itself
into Safe Mode again with a log message like this:
> {code}
>  14:00:10,666  WARN NameNodeResourceChecker:89 - Space available on
> volume '/dev/hda1' is 104357888, which is below the configured
> reserved amount 104857600
> 14:00:10,670  WARN FSNamesystem:3190 - NameNode low on available disk
> space. Entering safe mode.
> 14:00:10,670  INFO StateChange:3836 - STATE* Safe mode is ON.
> Resources are low on NN. Safe mode must be turned off manually.
> {code}
> From the shell, it looks like this:
> {code}
>  [cmccabe@vm1 h]$ ./bin/hdfs dfsadmin -safemode get
> Safe mode is ON
> [cmccabe@vm1 h]$ ./bin/hdfs dfsadmin -safemode leave
> Safe mode is OFF
> [cmccabe@vm1 h]$ ./bin/hdfs dfsadmin -safemode get
> Safe mode is ON
> {code}
> It seems like we should change the message about turning off safe mode manually, if turning
off safe mode manually does not actually work for the case where resources are low.  Probably
we need to explain that safe mode should be turned off manually *after* adding more resources.
 As it is, the error message seems misleading.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message