You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/09/15 04:11:45 UTC

[jira] [Commented] (AMBARI-13052) Stop-and-Start Upgrade: HDP 2.1->2.3 needs to stop services using 2.1, and start using 2.3

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

Hadoop QA commented on AMBARI-13052:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12755870/AMBARI-13052.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3780//console

This message is automatically generated.

> 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)