ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13633) Express Upgrade Fails When Starting Standby NameNode
Date Thu, 29 Oct 2015 22:39:28 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-13633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981473#comment-14981473
] 

Hudson commented on AMBARI-13633:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #3737 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3737/])
AMBARI-13633. Express Upgrade Fails When Starting Standby NameNode (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4690c8f0cbe30f672309234f9c85aec1255544c3])
* ambari-server/src/test/python/stacks/2.0.6/configs/nn_eu_standby.json
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py


> Express Upgrade Fails When Starting Standby NameNode
> ----------------------------------------------------
>
>                 Key: AMBARI-13633
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13633
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13633.patch
>
>
> When using HDFS/HA, the standby NN fails with:
> {noformat}
> 2015-10-27 19:25:50,330 ERROR namenode.NameNode (NameNode.java:main(1571)) - Failed to
start namenode.
> java.io.IOException: java.lang.RuntimeException: org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
Directory /hadoop/hdfs/namenode is in an inconsistent state: previous fs state should not
exist during upgrade. Finalize or rollback first.
> 	at org.apache.hadoop.hdfs.server.namenode.ha.BootstrapStandby.run(BootstrapStandby.java:425)
> 	at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1455)
> 	at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1566)
> Caused by: java.lang.RuntimeException: org.apache.hadoop.hdfs.server.common.InconsistentFSStateException:
Directory /hadoop/hdfs/namenode is in an inconsistent state: previous fs state should not
exist during upgrade. Finalize or rollback first.
> 	at org.apache.hadoop.hdfs.server.namenode.ha.BootstrapStandby$1.run(BootstrapStandby.java:116)
> 	at org.apache.hadoop.hdfs.server.namenode.ha.BootstrapStandby$1.run(BootstrapStandby.java:110)
> 	at org.apache.hadoop.security.SecurityUtil.doAsLoginUserOrFatal(SecurityUtil.java:415)
> 	at org.apache.hadoop.hdfs.server.namenode.ha.BootstrapStandby.run(BootstrapStandby.java:110)
> 	at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> 	at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> 	at org.apache.hadoop.hdfs.server.namenode.ha.BootstrapStandby.run(BootstrapStandby.java:420)
> 	... 2 more
> Caused by: org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory
/hadoop/hdfs/namenode is in an inconsistent state: previous fs state should not exist during
upgrade. Finalize or rollback first.
> 	at org.apache.hadoop.hdfs.server.namenode.FSImage.checkUpgrade(FSImage.java:362)
> 	at org.apache.hadoop.hdfs.server.namenode.ha.BootstrapStandby.doPreUpgrade(BootstrapStandby.java:269)
> 	at org.apache.hadoop.hdfs.server.namenode.ha.BootstrapStandby.doRun(BootstrapStandby.java:196)
> 	at org.apache.hadoop.hdfs.server.namenode.ha.BootstrapStandby.access$000(BootstrapStandby.java:76)
> 	at org.apache.hadoop.hdfs.server.namenode.ha.BootstrapStandby$1.run(BootstrapStandby.java:114)
> 	... 8 more
> 2015-10-27 19:25:50,336 INFO  util.ExitUtil (ExitUtil.java:terminate(124)) - Exiting
with status 1
> 2015-10-27 19:25:50,344 INFO  namenode.NameNode (LogAdapter.java:info(47)) - SHUTDOWN_MSG:
> /************************************************************
> SHUTDOWN_MSG: Shutting down NameNode at c6402.ambari.apache.org/192.168.64.102
> ************************************************************/
> {noformat}
>  {{-bootstrapStandby}} should not be an option on daemon startup, but rather just a separate
HDFS command to be run BEFORE starting.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message