[
https://issues.apache.org/jira/browse/YARN-7512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16401158#comment-16401158
]
Chandni Singh commented on YARN-7512:
-------------------------------------
[~leftnoteasy]
Just some comments.
{quote}1. Talked to [~csingh], existing upgrade only supports artifact, and all
other fields will be silently ignored. Probably we should rename the "upgrade"
to something like "set-image"?
{quote}
Initially, I am focusing on upgrade based on just artifact change. The design
doc does include other fields. Once basic upgrade is in place, the plan was to
enhance the feature.
{quote}2. Regarding to existing interactions between user and native services
to do updates. IIUC, this is workflow proposed in the design doc, plz correct
me if I was wrong:
a. User upload a new upgrade spec to HDFS.
b. User call upgrade service to read the new spec.
c. User call upgrade component(s) to update components and instances.
d. User manually set finalize or YARN will automatically set finalize of
services.
{quote}
There are not 4 steps but 3 steps. a) and b) are part of initializing the
service upgrade.
> Support service upgrade via YARN Service API and CLI
> ----------------------------------------------------
>
> Key: YARN-7512
> URL: https://issues.apache.org/jira/browse/YARN-7512
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Gour Saha
> Assignee: Chandni Singh
> Priority: Major
> Fix For: yarn-native-services
>
> Attachments: _In-Place Upgrade of Long-Running Applications in
> YARN_v1.pdf, _In-Place Upgrade of Long-Running Applications in YARN_v2.pdf
>
>
> YARN Service API and CLI needs to support service (and containers) upgrade in
> line with what Slider supported in SLIDER-787
> (http://slider.incubator.apache.org/docs/slider_specs/application_pkg_upgrade.html)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
