Community Articles
Find and share helpful community-sourced technical articles.
Labels (1)

PROBLEM STATEMENT: After finishing upgrade of all Hadoop components, I issued su - hdfs -c "hdfs dfsadmin -finalizeUpgrade" on active Namenode. However, NN UI shows all is good, until I failover to standby and standby becomes active - then again I got message that I should finalize my upgrade.


2015-10-27 18:16:04,954 - Task. Type: EXECUTE, Script: scripts/ - Function: prepare_non_rolling_upgrade
2015-10-27 18:16:05,044 - Preparing the NameNodes for a NonRolling (aka Express) Upgrade.
2015-10-27 18:16:05,045 - checked_call[' su hdfs -l -s /bin/bash -c 'curl -s '"'"',name=FSNamesystem'"'"' 1>/tmp/tmpKcaPrw 2>/tmp/tmpPjCQIr''] {'quiet': False}
2015-10-27 18:16:05,068 - checked_call returned (0, '')
2015-10-27 18:16:05,069 - checked_call[' su hdfs -l -s /bin/bash -c 'curl -s '"'"',name=FSNamesystem'"'"' 1>/tmp/tmpPIEyeS 2>/tmp/tmpOOXCrc''] {'quiet': False}
2015-10-27 18:16:05,092 - checked_call returned (0, '')
2015-10-27 18:16:05,093 - NameNode High Availability is enabled and this is the Active NameNode.
2015-10-27 18:16:05,093 - Enter SafeMode if not already in it.
2015-10-27 18:16:05,094 - Checkpoint the current namespace.
2015-10-27 18:16:05,094 - Backup the NameNode name directory's CURRENT folder.
2015-10-27 18:16:05,100 - Execute[('cp', '-ar', '/hadoop/hdfs/namenode/current', '/tmp/upgrades/2.2/namenode_ida8c06540_date162715_1/')] {'sudo': True}
2015-10-27 18:16:05,113 - Attempt to Finalize if there are any in-progress upgrades. This will return 255 if no upgrades are in progress.
2015-10-27 18:16:05,113 - checked_call['/usr/hdp/current/hadoop-hdfs-namenode/bin/hdfs dfsadmin -rollingUpgrade finalize'] {'logoutput': True, 'user': 'hdfs'}
FINALIZE rolling upgrade ...
There is no rolling upgrade in progress or rolling upgrade has already been finalized.
2015-10-27 18:16:08,213 - checked_call returned (0, 'FINALIZE rolling upgrade ...\nThere is no rolling upgrade in progress or rolling upgrade has already been finalized.')

ROOT CAUSE: This is a BUG in Ambari - [Hortonworks internal BUG URL for reference]

RESOLUTION: The above bug has taken care in Ambari2.2.0 version.

Upgrading to Ambari2.2.0 will resolved the issue.

Take a Tour of the Community
Don't have an account?
Version history
Last update:
‎12-26-2016 06:15 PM
Updated by:
Top Kudoed Authors
; ;