Manish, you stop HDFS then start HDFS on the standby name node right?
please looked at https://issues.apache.org/jira/browse/HDFS-5058 there are two solutions: 1) start HDFS on the active name node, nor SBN 2) copy {namenode.name.dir}/* to the SBN I advice #1. On Wed, Aug 7, 2013 at 3:00 PM, Manish Bhoge <manishbh...@rocketmail.com>wrote: > I have all configuration fine. But whenever i start namenode it fails with > a below exception. No clue where to fix this? > > "2013-08-07 02:56:22,754 FATAL > org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenode join" > > 2013-08-07 02:56:22,751 INFO org.apache.hadoop.hdfs.server.namenode.FSImage: > Number of files = 1 > 2013-08-07 02:56:22,751 INFO org.apache.hadoop.hdfs.server.namenode.FSImage: > Number of files under construction = 0 > 2013-08-07 02:56:22,752 INFO org.apache.hadoop.hdfs.server.namenode.FSImage: > Image file of size 115 loaded in 0 seconds. > 2013-08-07 02:56:22,752 INFO org.apache.hadoop.hdfs.server.namenode.FSImage: > Loaded image for txid 0 from > /data/1/dfs/nn/current/fsimage_0000000000000000000 > 2013-08-07 02:56:22,752 INFO org.apache.hadoop.hdfs.server.namenode.FSImage: > Reading > org.apache.hadoop.hdfs.server.namenode.RedundantEditLogInputStream@5f18223d > expecting start txid #1 > 2013-08-07 02:56:22,752 INFO > org.apache.hadoop.hdfs.server.namenode.EditLogInputStream: Fast-forwarding > stream '/data/1/dfs/nn/current/edits_0000000000000515247-0000000000000515255' > to transaction ID 1 > 2013-08-07 02:56:22,753 INFO > org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Stopping NameNode metrics > system... > 2013-08-07 02:56:22,754 INFO > org.apache.hadoop.metrics2.impl.MetricsSystemImpl: NameNode metrics system > stopped. > 2013-08-07 02:56:22,754 INFO > org.apache.hadoop.metrics2.impl.MetricsSystemImpl: NameNode metrics system > shutdown complete.2013-08-07 02:56:22,754 FATAL > org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenode join > java.io.IOException: There appears to be a gap in the edit log. We expected > txid 1, but got txid 515247. > >
