<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: hadoop cluster + Unable to start standby Namenode in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/hadoop-cluster-Unable-to-start-standby-Namenode/m-p/383140#M244837</link>
    <description>&lt;P&gt;=&amp;gt; If above steps still gives you issues then you can simply execute step 5 or below Cmd from Standby NN&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;DIV&gt;&lt;STRONG&gt;// Bootstrap Standby NameNode. This command copies the contents of the Active NameNode's metadata directories (including the namespace information and most recent checkpoint) to the Standby NameNode.&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;# hdfs namenode -bootstrapStandby&lt;BR /&gt;&lt;BR /&gt;Note: Step 1 to step 3 is process of creating new fsimage but if your Active NN is already up and running then I would directly login in to Standby and then perform bootstrapStandby operation&lt;/DIV&gt;</description>
    <pubDate>Mon, 05 Feb 2024 13:21:31 GMT</pubDate>
    <dc:creator>9een</dc:creator>
    <dc:date>2024-02-05T13:21:31Z</dc:date>
    <item>
      <title>hadoop cluster + Unable to start standby Namenode</title>
      <link>https://community.cloudera.com/t5/Support-Questions/hadoop-cluster-Unable-to-start-standby-Namenode/m-p/383097#M244817</link>
      <description>&lt;P&gt;we have HDP Hadoop cluster with two name-node services ( one active name-node and the secondary is the standby name-node )&lt;/P&gt;&lt;P&gt;due of unexpected electricity failure , the standby name-node failed to start with the flowing exception , while the active name-node starting successfully&lt;/P&gt;&lt;P&gt;2024-02-02 08:47:11,497 INFO common.Storage (Storage.java:tryLock(776)) - Lock on /hadoop/hdfs/namenode/in_use.lock acquired by nodename 36146@master1.delax.com&lt;BR /&gt;2024-02-02 08:47:11,891 INFO namenode.FSImage (FSImage.java:loadFSImageFile(745)) - Planning to load image: FSImageFile(file=/hadoop/hdfs/namenode/current/fsimage_0000000052670667141, cpktTxId=0000000052670667141)&lt;BR /&gt;2024-02-02 08:47:11,897 ERROR namenode.FSImage (FSImage.java:loadFSImage(693)) - Failed to load image from FSImageFile(file=/hadoop/hdfs/namenode/current/fsimage_0000000052670667141, cpktTxId=0000000052670667141)&lt;BR /&gt;java.io.IOException: Premature EOF from inputStream&lt;BR /&gt;at org.apache.hadoop.io.IOUtils.readFully(IOUtils.java:204)&lt;BR /&gt;at org.apache.hadoop.hdfs.server.namenode.FSImageFormat$LoaderDelegator.load(FSImageFormat.java:221)&lt;BR /&gt;at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:898)&lt;BR /&gt;at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:882)&lt;BR /&gt;at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImageFile(FSImage.java:755)&lt;BR /&gt;at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:686)&lt;BR /&gt;at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:303)&lt;BR /&gt;at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:1077)&lt;BR /&gt;at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:724)&lt;BR /&gt;at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:697)&lt;BR /&gt;at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:761)&lt;BR /&gt;at org.apache.hadoop.hdfs.server.namenode.NameNode.&amp;lt;init&amp;gt;(NameNode.java:1001)&lt;BR /&gt;at org.apache.hadoop.hdfs.server.namenode.NameNode.&amp;lt;init&amp;gt;(NameNode.java:985)&lt;BR /&gt;at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1710)&lt;BR /&gt;at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1778)&lt;BR /&gt;2024-02-02 08:47:12,238 WARN namenode.FSNamesystem (FSNamesystem.java:loadFromDisk(726)) - Encountered exception loading fsimage&lt;BR /&gt;java.io.IOException: Failed to load FSImage file, see error(s) above for more info.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;we can see from above exception - `Failed to load image from FSImageFile` , and seems it is as results of when machine failed because unexpected shutdown&lt;/P&gt;&lt;P&gt;as I understand one of the options to recover the standby name-node could be with the following procedure:&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;1. Put Active NN in safemode&lt;/P&gt;&lt;P&gt;sudo -u hdfs hdfs dfsadmin -safemode enter&lt;/P&gt;&lt;P&gt;2. Do a savenamespace operation on Active NN&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;sudo -u hdfs hdfs dfsadmin -saveNamespace&lt;/P&gt;&lt;P&gt;3. Leave Safemode&lt;/P&gt;&lt;P&gt;sudo -u hdfs hdfs dfsadmin -safemode leave&lt;/P&gt;&lt;P&gt;4. Login to Standby NN&lt;/P&gt;&lt;P&gt;5. Run below command on Standby namenode to get latest fsimage that we saved in above steps.&lt;/P&gt;&lt;P&gt;sudo -u hdfs hdfs namenode -bootstrapStandby -force&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;we glad to receive any suggestions , or if my above suggestion is good enough for our problem&lt;/P&gt;</description>
      <pubDate>Sat, 03 Feb 2024 22:23:10 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/hadoop-cluster-Unable-to-start-standby-Namenode/m-p/383097#M244817</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2024-02-03T22:23:10Z</dc:date>
    </item>
    <item>
      <title>Re: hadoop cluster + Unable to start standby Namenode</title>
      <link>https://community.cloudera.com/t5/Support-Questions/hadoop-cluster-Unable-to-start-standby-Namenode/m-p/383112#M244826</link>
      <description>&lt;P&gt;Approach you mentioned involves further downtime&amp;nbsp;&lt;/P&gt;&lt;P&gt;If your active NN is up and running then you can simply copy the latest fsimage from active NN data dir path to Standby NN data dir path and then try to start the standby NN once again&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 04 Feb 2024 18:00:47 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/hadoop-cluster-Unable-to-start-standby-Namenode/m-p/383112#M244826</guid>
      <dc:creator>9een</dc:creator>
      <dc:date>2024-02-04T18:00:47Z</dc:date>
    </item>
    <item>
      <title>Re: hadoop cluster + Unable to start standby Namenode</title>
      <link>https://community.cloudera.com/t5/Support-Questions/hadoop-cluster-Unable-to-start-standby-Namenode/m-p/383114#M244828</link>
      <description>&lt;P&gt;lets say I copy the fsimage from active to standby namenode&amp;nbsp; and then still we have a problem to start the namenode then&amp;nbsp; can I do the steps as already mentioned?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 04 Feb 2024 18:43:05 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/hadoop-cluster-Unable-to-start-standby-Namenode/m-p/383114#M244828</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2024-02-04T18:43:05Z</dc:date>
    </item>
    <item>
      <title>Re: hadoop cluster + Unable to start standby Namenode</title>
      <link>https://community.cloudera.com/t5/Support-Questions/hadoop-cluster-Unable-to-start-standby-Namenode/m-p/383140#M244837</link>
      <description>&lt;P&gt;=&amp;gt; If above steps still gives you issues then you can simply execute step 5 or below Cmd from Standby NN&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;DIV&gt;&lt;STRONG&gt;// Bootstrap Standby NameNode. This command copies the contents of the Active NameNode's metadata directories (including the namespace information and most recent checkpoint) to the Standby NameNode.&lt;/STRONG&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;# hdfs namenode -bootstrapStandby&lt;BR /&gt;&lt;BR /&gt;Note: Step 1 to step 3 is process of creating new fsimage but if your Active NN is already up and running then I would directly login in to Standby and then perform bootstrapStandby operation&lt;/DIV&gt;</description>
      <pubDate>Mon, 05 Feb 2024 13:21:31 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/hadoop-cluster-Unable-to-start-standby-Namenode/m-p/383140#M244837</guid>
      <dc:creator>9een</dc:creator>
      <dc:date>2024-02-05T13:21:31Z</dc:date>
    </item>
  </channel>
</rss>

