hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Li (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-3241) BackupNode can't start if its storage directory is not manually hacked
Date Tue, 10 Apr 2012 01:53:18 GMT
BackupNode can't start if its storage directory is not manually hacked
----------------------------------------------------------------------

                 Key: HDFS-3241
                 URL: https://issues.apache.org/jira/browse/HDFS-3241
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: name-node
    Affects Versions: 3.0.0
            Reporter: Brandon Li
            Priority: Minor


BackupNode can't start if its storage dir is not formatted (because it extends NameNode).
After I use "/bin/hadoop namenode -format" to format its storage directory, it still can't
start because the inconsistent namespace with primary namenode.

{noformat}
2012-04-09 18:33:16,464 ERROR namenode.NameNode (NameNode.java:main(958)) - Exception in namenode
join
java.io.IOException: Inconsistent namespace information:
NamespaceInfo has:
LV=-40;NS=1165721067;cTime=0;CID=CID-b8ced26a-4675-476d-b5fb-c9ad337be34a;BPID=BP-1658271424-10.10.10.191-1333658489893.
Storage has:
LV=-40;NS=403924869;cTime=0;CID=CID-57ce694a-172c-4da1-9cd6-d498615e4f1e;BPID=BP-4558626-10.10.10.48-1334021589986.
	at org.apache.hadoop.hdfs.server.protocol.NamespaceInfo.validateStorage(NamespaceInfo.java:109)
	at org.apache.hadoop.hdfs.server.namenode.BackupNode.registerWith(BackupNode.java:332)
	at org.apache.hadoop.hdfs.server.namenode.BackupNode.initialize(BackupNode.java:161)
	at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:546)
	at org.apache.hadoop.hdfs.server.namenode.BackupNode.<init>(BackupNode.java:86)
	at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:893)
{noformat}

The backup node started after I copied the VERSION file from the primary namenode storage
directory to that of the backup node.

This manual hack can be avoided if the backup node can format its local directory by requesting
VERSION info from the primary namenode.

  

--
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

        

Mime
View raw message