[
https://issues.apache.org/jira/browse/YARN-8298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586347#comment-16586347
]
Chandni Singh edited comment on YARN-8298 at 8/20/18 6:29 PM:
--------------------------------------------------------------
[~eyang] Supporting orchestration of upgrade by ServiceMaster requires much
more work and is blocked by https://issues.apache.org/jira/browse/YARN-8665
There is another major problem with express upgrade. The instances of a single
component should also be done one by one (rolling fashion). Otherwise, upgrade
can cause disruption in component availability. One of the main reasons behind
upgrade is that service is not disrupted. However if we upgrade all the
instances in parallel, then failure in upgrade causes disruption.
There are 2 ways to proceed:
1. Support canceling upgrade first
https://issues.apache.org/jira/browse/YARN-8665 and then re-work this jira
2. We merge this way of express upgrade where all instances are upgraded in
parallel. It is a convenient way for dev testing. Work on YARN-8665 and then
modify express upgrade.
I am fine with either way.
was (Author: csingh):
[~eyang] Supporting orchestration of upgrade by ServiceMaster requires much
more work and is blocked by https://issues.apache.org/jira/browse/YARN-8665
There is another major problem with express upgrade. The instances of a single
component should also be done one by one (rolling fashion). Otherwise, upgrade
can cause disruption in component availability. One of the main reasons behind
upgrade is that service is not disrupted. However if we upgrade all the
instances in parallel, then failure in upgrade causes disruption.
There are 2 ways to proceed:
1. Support canceling upgrade first
https://issues.apache.org/jira/browse/YARN-8665 and then re-work this jira
2. We merge this way of express upgrade where all instances are upgraded in
parallel. It is a convenient way for dev testing.
I am fine with either 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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
