[
https://issues.apache.org/jira/browse/YARN-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295133#comment-15295133
]
Arun Suresh edited comment on YARN-5087 at 5/23/16 7:34 PM:
------------------------------------------------------------
[~vinodkv], [~leftnoteasy], [~jianhe], [~mding] We were thinking of reusing /
piggy-backing some of the stuff done in YARN-1197. Essentially, we would like
the AM to issue a request to the RM to update the container execution type in
an allocate request and we would like to be notified of when that request is
satisfied in the response.
We were wondering if it is possible to combine the increase resources, decrease
resources and change container execution type requests into a single
*UpdateContainerRequest* type. The RM can then decide what type of change
request it is.
Also, in a similar vein, we can merge the Increased/Decreased Containers and
the Updated containerType response into the same list in the AllocateResponse.
To be honest, I feel even that is superfluous, since we already have a List of
{{Container}}s in the {{allocatedContainers}} field of the response which has
all the information about a container (Container Resource and ExecutionType).
The AM can then figure out if its request has been satisfied.
adding [~subru], [~curino], [~kkaranasos] to the conversation.
was (Author: asuresh):
[~vinodkv], [~leftnoteasy], [~jianhe], [~mding] We were thinking of reusing /
piggy-backing some of the stuff done in YARN-1197. Essentially, we would like
the AM to issue a request to the RM update the container type in an allocate
request and we would like to be notified of when that request is satisfied in
the response.
We were wondering if it is possible to combine the increase resources, decrease
resources and change container type requests into a single
*UpdateContainerRequest* type. The RM can then decide what type of change
request it is.
Also, in a similar vein, we can merge the Increased/Decreased Containers and
the Updated containerType response into the same list in the AllocateResponse.
To be honest, I feel even that is superfluous, since we already have a
List<Container> allocatedContainers list and the ContainerToken containers all
the information about a container (Container Resource and ExecutionType). The
AM can then figure out if its request has been satisfied.
adding [~subru], [~curino], [~kkaranasos] in the conversation.
> Expose API to allow AM to request for change of container ExecutionType
> -----------------------------------------------------------------------
>
> Key: YARN-5087
> URL: https://issues.apache.org/jira/browse/YARN-5087
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Arun Suresh
> Assignee: Arun Suresh
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
