[
https://issues.apache.org/jira/browse/YARN-7512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16401298#comment-16401298
]
Billie Rinaldi commented on YARN-7512:
--------------------------------------
bq. 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
Sorry, this comment I made was really unclear. I completely agree that version
should appear as a field in the json, I was just questioning whether the
version should appear in the file name of the file that is saved to HDFS.
> 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]