[
https://issues.apache.org/jira/browse/YARN-8298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586154#comment-16586154
]
Chandni Singh edited comment on YARN-8298 at 8/20/18 4:30 PM:
--------------------------------------------------------------
[~eyang]
Even though the patch 2 referenced resolveCompsDependency, it wasn't being used
to orchestrate upgrade of comp instances in any way.
If we need to orchestrate upgrade of instances based on component dependency,
it requires the support to cancel the current upgrade. For, example if upgrade
of compA fails, then compB upgrade will not be triggered as well.
was (Author: csingh):
[~eyang]
Even though the patch 2 referenced resolveCompsDependency, it wasn't being used
to orchestrate upgrade of comp instances in any way.
> 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
>
>
> 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]
