hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Chu (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-3472) initializeSharedEdits should warn if a shared edits dir is not configured
Date Fri, 26 Oct 2012 08:55:12 GMT

     [ https://issues.apache.org/jira/browse/HDFS-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Stephen Chu resolved HDFS-3472.

          Resolution: Not A Problem
    Target Version/s:   (was: )

This seems to no longer be a problem. When I run initializeSharedEdits without configuring
a shared edits dir, I get the following:

12/10/26 01:49:40 FATAL namenode.NameNode: No shared edits directory configured for namespace
null namenode null
12/10/26 01:49:40 INFO util.ExitUtil: Exiting with status 0
12/10/26 01:49:40 INFO namenode.NameNode: SHUTDOWN_MSG: 
SHUTDOWN_MSG: Shutting down NameNode at cs-10-20-193-70.cloud.cloudera.com/
> initializeSharedEdits should warn if a shared edits dir is not configured
> -------------------------------------------------------------------------
>                 Key: HDFS-3472
>                 URL: https://issues.apache.org/jira/browse/HDFS-3472
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: ha
>    Affects Versions: 2.0.0-alpha
>            Reporter: Eli Collins
>            Priority: Minor
>              Labels: newbie
> Running initializeSharedEdits w/o a shared edits dir currently yields the following rather
than a user friendly message about a shared edits dir not being configured.
> {noformat}
> 12/05/29 13:03:08 INFO common.Storage: Storage directory /tmp/hadoop-hdfs/dfs/name does
not exist. 12/05/29 13:03:08 ERROR namenode.NameNode: Could not initialize shared edits dir
org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /tmp/hadoop-hdfs/dfs/name
is in an inconsistent state: storage directory does not exist or is not accessible. at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverStorageDirs(FSImage.java:274)
at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:180)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:498)
at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:390)
at org.apache.hadoop.hdfs.server.namenode.NameNode.initializeSharedEdits(NameNode.java:818)
at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1118) at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1193)
12/05/29 13:03:08 INFO namenode.NameNode: SHUTDOWN_MSG: /************************************************************
SHUTDOWN_MSG: Shutting down NameNode at centos60-17.ent.cloudera.com/ ************************************************************/
> {noformat}

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

View raw message