[ 
https://issues.apache.org/jira/browse/YARN-7512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16401405#comment-16401405
 ] 

Eric Yang commented on YARN-7512:
---------------------------------

In YARN-8018, we discussed that when AM is online, ServiceClient sends JSON to 
AM, and AM commit the file with a new version number after completing 
operations.  When AM is offline, ServiceClient checks for version number in 
client supplied JSON.  ServiceClient will use client set version number.  If 
version number doesn't exist, then ServiceClient use existing version from HDFS 
and increment by one.  This approach will resolve the version number conflicts, 
and provide a way to let user reset the number, if hdfs copy is corrupted.

> 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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to