You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2014/08/07 22:09:13 UTC

[jira] [Commented] (SLIDER-167) Automatically copy slider-agent.tar.gz when creating an application

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

Sumit Mohanty commented on SLIDER-167:
--------------------------------------

If each application instance has their own copy of AppMaster jars (today they do) and the Agent tarball then user can selectively upgrade Slider on a per app-instance basis. Because it cannot be prevented that users have a per app-instance copy of Slider, we might as well assume it to be the standard.

This brings in few scenarios:
* Version mismatch between Slider Client, AppMaster, and Agent
** Slider should implement a mechanism to log version mismatches or even WARN if there ever is incompatible changes
* Upgrade of Slider is now a per app-instance activity
** Slider should plan on some form of tooling to make it easier to upgrade multiple apps at the same time
* If Slider upgrade requires app-instance to be stopped then the above procedure should be valid
* If Slider supports rolling upgrade then also the above approach may hold
** Rolling upgrade requires Slider-Client/AppMaster/Agent libraries to be upgraded and then do a AppMaster restart followed by orchestrated container restarts (assuming YARN will add capability to this end if necessary)
** Assumption being while AppMaster and Containers are active they won't get affected by updating Slider libraries in HDFS
** We may need a command to prepare AppMaster for upgrade where it may store some additional information such as old/new version, not entertain any form of update including allocating new containers if any fail
** Issue an AppMaster restart such that the restart picks the new version of AppMaster
** Issue a rolling restart of all containers

> Automatically copy slider-agent.tar.gz when creating an application
> -------------------------------------------------------------------
>
>                 Key: SLIDER-167
>                 URL: https://issues.apache.org/jira/browse/SLIDER-167
>             Project: Slider
>          Issue Type: Bug
>          Components: client
>    Affects Versions: Slider 0.40
>            Reporter: Sumit Mohanty
>            Assignee: Steve Loughran
>
> Currently, user need to explicitly provide the location of slider-agent.tar.gz when creating an application. However, the file is available at the deployment location for slider client. The create command should automatically copy the agent tarball to an application instance specific location by reading it from the local file system (<slider deployment dir>/agent/slider-agent.tar.gz). 
> This ensures that the agent tarball is in sync with the version of slider used to create the application instance.



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