ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-12228) Oozie Rolling Upgrade Orchestration Is Incorrect
Date Wed, 01 Jul 2015 23:23:06 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-12228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14611168#comment-14611168
] 

Hudson commented on AMBARI-12228:
---------------------------------

FAILURE: Integrated in Ambari-branch-2.1 #162 (See [https://builds.apache.org/job/Ambari-branch-2.1/162/])
AMBARI-12228 - Oozie Rolling Upgrade Orchestration Is Incorrect (jonathanhurley) (jhurley:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=63ee3926fb0f188e98f122c5ec7ead72cfc5381f)
* ambari-server/src/test/python/stacks/2.2/configs/oozie-upgrade.json
* ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ExecuteHostType.java
* ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/TaskWrapperBuilder.java
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml
* ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml
* ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py
* ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/ExecuteTask.java
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.2.xml
* ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/storm_upgrade.py
* ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py
* ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server_upgrade.py


> Oozie Rolling Upgrade Orchestration Is Incorrect
> ------------------------------------------------
>
>                 Key: AMBARI-12228
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12228
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.1.0
>
>
> Here is an example of the new orchestration for an upgrade from 2.2 to 2.3
> - Before Upgrade Begins
> -# Execute a custom script to stop all oozie servers, one at a time
> -# Execute the database upgrade using the 2.3 bits
> -# Execute the sharelib creation and upload using the 2.3 bits
> - For each Oozie server, which is currently down
> -# backup the oozie configurations
> -# conf-select and hdp-select
> -# restore configurations
> -# Prepare /usr/hdp/current/oozie/libext-customer and gets ready to upgrade the WAR
> -# \{oozie_setup_sh\} prepare-war \{oozie_secure\} -d \{oozie_libext_customer_dir\}
> -# Start the Oozie server
> On a downgrade, we will perform a similar series of steps, except a few differences:
> - No database upgrade will be performed
> - The bits used to generate the sharelib are going to be the downgrade stacks, ie 2.2



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message