[
https://issues.apache.org/jira/browse/YARN-7512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394233#comment-16394233
]
Billie Rinaldi commented on YARN-7512:
--------------------------------------
A couple of late comments:
* If there are only two versions allowed at a time, perhaps we shouldn't
include the version number in the upgrade service json, instead calling it
something like \{service_name}_upgrade.json or \{service_name}_next.json. That
would also have the advantage of not restricting the characters that can appear
in the version string.
* Is the ServiceClient API section missing a method to specify the new Service?
* If there is only one Service json that can be upgraded to, it seems like we
should remove the version parameter from the actionUpgrade(String appName,
String version) method.
> 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
>
>
> 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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
