[jira] [Comment Edited] (SLIDER-290) Slider upgrade

["Sumit Mohanty (JIRA)" <ji...@apache.org>]

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

Sumit Mohanty edited comment on SLIDER-290 at 8/7/14 8:04 PM:
--------------------------------------------------------------

Scenario: User is using Stack version 2.6 with Slider version 1 and has deployed application package version 1. A new version of Stack (Stack-2.7) is released and a new version of Slider (Slider-2) and the AppPkg (AppPkg-2) is available.

This JIRA is not addressing how user may upgrade their App from AppPkg-1 to AppPkg-2.

User choices:

h3.Upgrade the Stack but not Slider

Essentially, YARN, HDFS, ZK, etc. gets upgraded. If its not a rolling upgrade then the application instance is stopped prior to hadoop/Stack upgrade and then restarted after upgrade. If its a rolling upgrade then the application instance should not be impacted.

This is supported if
*  YARN/HDFS/ZK are backwards compatible

Steps:
* User follows the standard upgrade steps for hadoop/Stack
* If its not a rolling upgrade then user needs to stop the application instance and then upgrade Stack
* If its a rolling upgrade then user need not stop the application instance

h3.Upgrade Slider but not the Stack
Slider has some bug fixes and feature enhancements and is backward compatible with existing version of HDSF/YARN/ZK.

h4. App instance can be stopped
Steps:
* Stop the app instance
* Deploy the latest Slider version
* Update the copy of slider-agent.tar.gz
* Update the AppMaster lib jars
* Start the app instance

h4. App instance cannot be stopped
_This is not supported yet._ This requires a way to update the AM (restart AM with a different launch context to reflect new version of AM). Once that is supported, along with AM, the Slider-Agent and client can be upgraded. Then with AM restart followed by an orchestrated container restart can perform Slider upgrade without application having to get restarted.



was (Author: sumitmohanty):
Scenario: User is using an older version of Stack (e.g. Stack-2.6) with an older version of Slider (Slider-1) and is running an older version of an application package (AppPkg-1). A new version of Stack (Stack-2.7) is released and a new version of Slider (Slider-2) and the AppPkg (AppPkg-2) is available.

This JIRA is not addressing how user may upgrade their App from AppPkg-1 to AppPkg-2.

User choices:

h3.Upgrade the Stack but not Slider

Essentially, YARN, HDFS, ZK, etc. gets upgraded. If its not a rolling upgrade then the application instance is stopped prior to hadoop upgrade and then restarted after upgrade. If its a rolling upgrade then the application instance should not be impacted.

This is supported if
*  YARN/HDFS/ZK are backwards compatible

Steps:
* User follows the standard upgrade steps for hadoop
* If its not a rolling upgrade then user needs to stop the application instance and then upgrade Stack
* If its a rolling upgrade then user need not stop the application instance

h3.Upgrade Slider but not the Stack
Slider has some bug fixes or feature enhancements and is backward compatible with existing version of HDSF/YARN/ZK.

h4. App instance can be stopped
Steps:
* Stop the app instance
* Deploy the latest Slider
* Update the copy of slider-agent.tar.gz
* Start the app instance

h4. App instance cannot be stopped
This is not supported. This requires a way to update the AM (restart AM with a different launch context


> Slider upgrade
> --------------
>
>                 Key: SLIDER-290
>                 URL: https://issues.apache.org/jira/browse/SLIDER-290
>             Project: Slider
>          Issue Type: Bug
>          Components: agent, appmaster
>    Affects Versions: Slider 0.50
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>
> Discuss what happens when Slider is upgraded or how a user can upgrade Slider while keeping the version of the application instance constant.



--
This message was sent by Atlassian JIRA
(v6.2#6252)