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

Eric Yang commented on YARN-8298:
---------------------------------

[~csingh] Rolling upgrade on top of express upgrade is novelty idea, but most 
of the uninterrupted logic needs to come from software that hosted in the 
container rather than the upgrade framework itself.  It would be good to 
proceed with option 2.  We have built sufficient number of knobs for individual 
container to upgrade in a rolling fashion.  However, it will depend on external 
orchestrator to perform the rolling upgrade.  Express upgrade is design to be 
atomic, therefore, it simplifies upgrade process by doing all instances of a 
component in parallel.  Docker container takes only a few second to stop and 
start, therefore, the interruption time is minimized to few seconds.  By having 
both features built, user can choose one or the other.  This approach matches 
perfectly with Ambari definition of rolling upgrade, and express upgrade 
respectively.



> Yarn Service Upgrade: Support express upgrade of a service
> ----------------------------------------------------------
>
>                 Key: YARN-8298
>                 URL: https://issues.apache.org/jira/browse/YARN-8298
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>    Affects Versions: 3.1.1
>            Reporter: Chandni Singh
>            Assignee: Chandni Singh
>            Priority: Major
>         Attachments: YARN-8298.001.patch, YARN-8298.002.patch, 
> YARN-8298.003.patch, YARN-8298.004.patch
>
>
> Currently service upgrade involves 2 steps
>  * initiate upgrade by providing new spec
>  * trigger upgrade of each instance/component
>  
> We need to add the ability to upgrade the service in one shot:
>  # Aborting the upgrade will not be supported
>  # Upgrade finalization will be done automatically.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to