ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Theodore Omtzigt (JIRA)" <>
Subject [jira] [Commented] (AMBARI-13462) NameNode fails to start due to unexpected version of storage directory
Date Sun, 18 Oct 2015 22:14:05 GMT


Theodore Omtzigt commented on AMBARI-13462:

Sumit: good call on the /opt/hadoop-2.6.0 jars. Stupidity on our side: another engineer was/is
developing an Ansible playbook to install Hadoop and designed a setup where the JDK installation
also sets the HADOOP_PREFIX environment variable. So that got picked up by the ambari agent
resulting in our troubles.

Clearly this was NOT a fresh install as I reported in the bug report. When I cleaned out the
remnants of the Ansible playbook that set the HADOOP_PREFIX variable, the HDP 2.3.2 cluster
came up in without a hitch.

This is thus not a bug in Ambari/HDP, but squarely our mistakes and poor engineering process.
Terribly sorry to have occupied your time. Thank you very much for your support, and the debug
process that you presented. That clearly was invaluable to us. Thank you, and we can close
this bug ticket.

> NameNode fails to start due to unexpected version of storage directory
> ----------------------------------------------------------------------
>                 Key: AMBARI-13462
>                 URL:
>             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 ( - 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

View raw message