Chandni Singh commented on YARN-7939:


Upgraded is either 2 steps when finalization is done automatically, or 3 steps 
when finalization is done manually:

Step 1: Initiate service level upgrade. This requires posting the newer spec. 
Here is an example:
"name": "test1",
"version" : "v2",
"state": "UPGRADING",
"components" :
"name": "sleeper",
"number_of_containers": 2,
"launch_command": "sleep 1200000",
"resource": {
"cpus": 1,
"memory": "256"
This json is the spec json and not the state json. 

There is no {{NEEDS_UPGRADE}} state at service level, so the json that you 
posted in your example for service level is incorrect.


Step 2: Trigger upgrade of component or individual component instances.

An example of this request is
"state": "UPGRADING",
"component_instance_name": "sleeper-0"

> Yarn Service Upgrade: add support to upgrade a component instance 
> ------------------------------------------------------------------
>                 Key: YARN-7939
>                 URL: https://issues.apache.org/jira/browse/YARN-7939
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Chandni Singh
>            Assignee: Chandni Singh
>            Priority: Major
>         Attachments: YARN-7939.001.patch, YARN-7939.002.patch, 
> YARN-7939.003.patch
> Yarn core supports in-place upgrade of containers. A yarn service can 
> leverage that to provide in-place upgrade of component instances. Please see 
> YARN-7512 for details.
> Will add support to upgrade a single component instance first and then 
> iteratively add other APIs and features.

This message was sent by Atlassian JIRA

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