Alejandro Fernandez created AMBARI-13723:
--------------------------------------------
Summary: Express Upgrade: HDP 2.1->2.3 must uninstall 2.1 bits
before starting on 2.3
Key: AMBARI-13723
URL: https://issues.apache.org/jira/browse/AMBARI-13723
Project: Ambari
Issue Type: Story
Components: ambari-server
Affects Versions: 2.2.0, 2.1.3
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
Fix For: 2.2.0, 2.1.3
We found a major flaw in the Express Upgrade from 2.1->2.3. Basically, "hadoop"
bin still points to the old binary because we had to install HDP 2.3 while 2.1
bits still existed.
*Manual Upgrade Instructions:*
* Stop all services using 2.1
* yum erase hadoop hdfs hive … (this will remove scripts /usr/bin/hadoop,
/usr/bin/hdfs, /usr/bin/hive, etc/)
* yum install hadoop_2_3_* hdfs_2_3_* hive_2_3_* (rpm should point
/usr/bin/hadoop -> /usr/hdp/current/hadoop-client/bin/hadoop)
* Change the version to 2.3 (hdp-select, conf-select, etc.)
* Start all services, and hence MR Service Check passes with "hadoop" command
*Express Upgrade:*
* Install HDP 2.3 bits. We reused the RU framework that relies on a 2 step
process: install bits, perform upgrade. Hence, /usr/bin/hadoop is still using
2.1 bits
* Stop all services using 2.1
* Change the version to 2.3 (hdp-select, conf-select, etc.)
* Start all services, will fail on MR Service Check because ExecuteHadoop()
resource calls "hadoop" command, which is still pointing to 2.1 bits!
One solution is for the orchestration to remove the 2.1 bits before starting
using 2.3.
Uninstalling the 2.1 bits will remove /usr/bin/hadoop, but when we call
"hdp-select set hadoop-client <new_version>" it will create the symlink
/usr/bin/hadoop -> /usr/hdp/current/hadoop-client/bin/hadoop
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
