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

["Ted Yu (JIRA)" <ji...@apache.org>]

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

Ted Yu updated SLIDER-226:
--------------------------

    Description: 
build 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.

  was:
SLIDER-223 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.


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