[
https://issues.apache.org/jira/browse/YARN-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746387#comment-15746387
]
Arun Suresh commented on YARN-3866:
-----------------------------------
[~leftnoteasy], wondering if updating yarn_service_proto as per
[comment|https://issues.apache.org/jira/browse/YARN-3866?focusedCommentId=15736065&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15736065]
made sense..
Also, was just wondering, given that we are deprecating this, wondering if it
is ok to just remove it altogether in 3.x releases, since maintaining both APIs
would be burdensome (or can we just throw some "NotSupportedAnymoreException").
Not sure what the EOL guidelines for APIs are.
> 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-branch-2.8.addendum.1.patch,
> YARN-3866-branch-2.8.addendum.2.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
