hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Isaacson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3612) Single namenode image directory config warning can be improved
Date Wed, 11 Jul 2012 23:45:35 GMT

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

Andy Isaacson commented on HDFS-3612:

Harsh - they're slightly different warnings, about name.dir and edits.dir respectively.  Since
the user needs to take two different actions to fix the problem, I think two warnings is reasonable.

As an admin, I'd be annoyed to get just the name.dir error, grumble, fix it, restart, get
the edits.dir error, gruble louder, fix it, restart ...
> Single namenode image directory config warning can be improved
> --------------------------------------------------------------
>                 Key: HDFS-3612
>                 URL: https://issues.apache.org/jira/browse/HDFS-3612
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 2.0.0-alpha
>            Reporter: Harsh J
>            Priority: Trivial
>              Labels: newbie
> Currently, if you configure the NameNode to run with just one dfs.namenode.name.dir directory,
it prints:
> {code}
> 12/07/08 20:00:22 WARN namenode.FSNamesystem: Only one dfs.namenode.name.dir directory
configured , beware data loss!{code}
> We can improve this in a few ways as it is slightly ambiguous:
> # Fix punctuation spacing, there's always a space after a punctuation mark but never
before one.
> # Perhaps the message is better printed with a reason of why it may cause a scare of
data loss. For instance, we can print "Detected a single storage directory in dfs.namenode.name.dir
configuration. Beware of dataloss due to lack of redundant storage directories" or so.

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


View raw message