hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-486) Change startContainer NM API to accept Container as a parameter and make ContainerLaunchContext user land
Date Thu, 11 Apr 2013 22:19:16 GMT

    [ https://issues.apache.org/jira/browse/YARN-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629476#comment-13629476
] 

Vinod Kumar Vavilapalli commented on YARN-486:
----------------------------------------------

I merged YARN-319 into branch-2. But YARN-488 won't be merged yet because it is a WINDOWS
only change, so can you upload a patch for branch-2? Tx.
                
> 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: Xuan Gong
>         Attachments: YARN-486.1.patch, YARN-486-20130410.txt, YARN-486.2.patch, YARN-486.3.patch,
YARN-486.4.patch, YARN-486.5.patch, YARN-486.6.patch
>
>
> 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

Mime
View raw message