[
https://issues.apache.org/jira/browse/YARN-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15736065#comment-15736065
]
Arun Suresh commented on YARN-3866:
-----------------------------------
Thanks for working on the [~leftnoteasy],
In, yarn_service_protos.proto, instead of incrementing the index number of
*am_rm_token* and *application_priority*, you can probably just change the
index of *updated_container* to 16 and leave the other 2 as it is. That way in
the branch-2 and trunk patch, you will not have conflict with *collector_addr*
field, which is 14.
+1 otherwise.
> AM-RM protocol changes to support container resizing
> ----------------------------------------------------
>
> Key: YARN-3866
> URL: https://issues.apache.org/jira/browse/YARN-3866
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: api
> Reporter: MENG DING
> Assignee: MENG DING
> Priority: Blocker
> Fix For: 2.8.0, 3.0.0-alpha1
>
> Attachments: YARN-3866-YARN-1197.4.patch,
> YARN-3866-branch-2.8.addendum.1.patch, YARN-3866.1.patch, YARN-3866.2.patch,
> YARN-3866.3.patch
>
>
> YARN-1447 and YARN-1448 are outdated.
> This ticket deals with AM-RM Protocol changes to support container resize
> according to the latest design in YARN-1197.
> 1) Add increase/decrease requests in AllocateRequest
> 2) Get approved increase/decrease requests from RM in AllocateResponse
> 3) Add relevant test cases
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
