[
https://issues.apache.org/jira/browse/AMBARI-13462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962469#comment-14962469
]
Sumit Mohanty commented on AMBARI-13462:
----------------------------------------
I just deployed {{2.3.2.0-2950}} and could not reproduce this issue. What I
noticed is that the version expected is {{63}} so not sure why namenode is
expecting 60 in your case. Can you check if the namenode process when it starts
is using correct version of the binaries.
Can you try to start manually and check - you can get the actual command from
the command output in Ambari. It will be similar to:
{code}
export HADOOP_LIBEXEC_DIR=/usr/hdp/current/hadoop-client/libexec
/var/lib/ambari-agent/ambari-sudo.sh su hdfs -l -s /bin/bash -c 'ulimit -c
unlimited ; /usr/hdp/current/hadoop-client/sbin/hadoop-daemon.sh --config
/usr/hdp/current/hadoop-client/conf start namenode'
{code}
What does {{hdp-select | grep namenode}} show?
> NameNode fails to start due to unexpected version of storage directory
> ----------------------------------------------------------------------
>
> Key: AMBARI-13462
> URL: https://issues.apache.org/jira/browse/AMBARI-13462
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.2
> Environment: Ubuntu 14.04 LTS fresh install
> Reporter: Theodore Omtzigt
>
> NameNode service does not start on fresh install through Wizard.
> 2015-10-18 10:18:54,427 FATAL namenode.NameNode (NameNode.java:main(1509)) -
> Failed to start namenode.
> org.apache.hadoop.hdfs.server.common.IncorrectVersionException: Unexpected
> version of storage directory /hadoop/hdfs/namenode. Reported: -63. Expecting
> = -60.
> Removing the content of /hadoop/hdfs/namenode, and restarting the NameNode
> through the Ambari server, yields a repeatable process to trigger this bug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
