[
https://issues.apache.org/jira/browse/YARN-8298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16574051#comment-16574051
]
Eric Yang commented on YARN-8298:
---------------------------------
[~csingh] While developing this patch, it was intended for the patch to run
with Hadoop 3.1.2 CLI, and issue upgrade command to ServiceAM started by Hadoop
3.1.1. This is the reason that orchestration logic runs in ServiceClient as
part of resource manager instead of ServiceAM. From architectural point of
view, it would be best for upgrade logic to run in ServiceAM. Hadoop 3.1.1
ServiceAM does not have express upgrade logic. Therefore, express upgrade is
triggered using ServiceState that can be understood by older ServiceAM. For
architectural correctness, it is in our interest to introduce a ServiceState
that can be understood by ServiceAM as express upgrade. This helps us to move
orchestration logic from ServiceClient to ServiceMaster. RM can be relief from
upgrade logic burden.
This would be an incompatible change to ServiceAM to gain new express upgrade
abilities. Therefore, I remove 3.1.2 from targeted version.
> 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
>
>
> 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]
