[
https://issues.apache.org/jira/browse/YARN-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605946#comment-13605946
]
Bikas Saha commented on YARN-486:
---------------------------------
Not quite. The container is not embedded into CLC. It is added as parameter to
startContainer() API. It is always available at that time. CLC becomes only
user land stuff like env, resources etc.
> Change startContainer NM API to accept Container as a parameter and make
> ContainerLaunchContext user land
> ---------------------------------------------------------------------------------------------------------
>
> Key: YARN-486
> URL: https://issues.apache.org/jira/browse/YARN-486
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Bikas Saha
>
> Currently, id, resource request etc need to be copied over from Container to
> ContainerLaunchContext. This can be brittle. Also it leads to duplication of
> information (such as Resource from CLC and Resource from Container and
> Container.tokens). Sending Container directly to startContainer solves these
> problems. It also makes CLC clean by only having stuff in it that it set by
> the client/AM.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
