Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 5 Nov 2015 03:28:27 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12910496.1446673026000.159353.1446694107784@Atlassian.JIRA>
In-Reply-To: <JIRA.12910496.1446673026000@Atlassian.JIRA>
References: <JIRA.12910496.1446673026000@Atlassian.JIRA>
 <JIRA.12910496.1446673026708@arcas>
Subject: [jira] [Commented] (AMBARI-13723) Express Upgrade: HDP 2.1->2.3
 must uninstall 2.1 bits before starting on 2.3
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/AMBARI-13723?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14=
991050#comment-14991050 ]=20

Hudson commented on AMBARI-13723:
---------------------------------

FAILURE: Integrated in Ambari-branch-2.1 #802 (See [https://builds.apache.o=
rg/job/Ambari-branch-2.1/802/])
AMBARI-13723. Express Upgrade: HDP 2.1->2.3 must uninstall 2.1 bits (aferna=
ndez: [http://git-wip-us.apache.org/repos/asf?p=3Dambari.git&a=3Dcommit&h=
=3D1f5545766fd619c277fd830ec6f48e4d74035e42])
* ambari-server/src/main/resources/custom_actions/scripts/remove_bits.py
* ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgra=
de-2.3.xml


> 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
>
>         Attachments: AMBARI-13723.trunk.patch
>
>
> We found a major flaw in the Express Upgrade from 2.1->2.3. Basically, "h=
adoop" 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 =E2=80=A6 (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/b=
in/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" com=
mand
> *Express Upgrade:*
> * Install HDP 2.3 bits. We reused the RU framework that relies on a 2 ste=
p process: install bits, perform upgrade. Hence, /usr/bin/hadoop is still u=
sing 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 start=
ing 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)