ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Fernandez (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-13052) Stop-and-Start Upgrade: HDP 2.1->2.3 needs to stop services using 2.1, and start using 2.3
Date Tue, 15 Sep 2015 22:12:46 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-13052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alejandro Fernandez updated AMBARI-13052:
-----------------------------------------
    Attachment: AMBARI-13052.patch

> Stop-and-Start Upgrade: HDP 2.1->2.3 needs to stop services using 2.1, and start using
2.3
> ------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13052
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13052
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.2.0
>
>         Attachments: AMBARI-13052.patch
>
>
> For a Stop-and-Start Upgrade from HDP 2.1 -> 2.3, we need to stop all services using
the scripts for HDP 2.1, and then start them using HDP 2.3.
> Today, during an Upgrade, we currently set the desired stack id when we process Upgrade
Pack and insert the upgrade record. That means that all start/stop commands use the scripts
from the desired stack.
> Instead, we need a Server Side Action to be called right before we run "hdp-select set
all" that will change the desired stack id to the new version; this will permit stopping on
the old version, and starting on the new version.
> When we downgrade, we commence the orchestration again, and we again call the Server
Side Action to change the desired stack id, this time to the starting version.



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

Mime
View raw message