You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2014/07/18 02:17:04 UTC

[jira] [Commented] (SLIDER-226) Provide mechanism for rolling upgrade

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

Ted Yu commented on SLIDER-226:
-------------------------------

Currently NodeEntry keeps count of live and releasing instances.
For rolling upgrade, we need more information - e.g. reference to image file which backs a particular entry.
This would allow helper method in NodeMap to decide which instance to release.

> Provide mechanism for rolling upgrade
> -------------------------------------
>
>                 Key: SLIDER-226
>                 URL: https://issues.apache.org/jira/browse/SLIDER-226
>             Project: Slider
>          Issue Type: Improvement
>            Reporter: Ted Yu
>
> update action paves the road for supporting rolling upgrade on Slider deployed cluster.
> User can specify a different image for a running cluster with N instances for role R.
> The rolling upgrade would restart each of the N instances while maintaining the invariant that there're at least N-1 active instances for role R.
> After restart, new image would be effective.
> This capability would, e.g., allow HBase to perform compatibility check across releases.



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