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-641) Make AMLauncher in RM Use NMClient
Date Fri, 07 Jun 2013 18:24:20 GMT

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

Vinod Kumar Vavilapalli commented on YARN-641:

*sigh* It seems like we'll have to move the tests in yarn-client to yarn-server-tests. Maven
is imposing a single dependency graph overall and not per scope. Once we do this, we should
perhaps rename server-tests to be integration - that's what it does.
> Make AMLauncher in RM Use NMClient
> ----------------------------------
>                 Key: YARN-641
>                 URL: https://issues.apache.org/jira/browse/YARN-641
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Zhijie Shen
>            Assignee: Zhijie Shen
> YARN-422 adds NMClient. RM's AMLauncher is responsible for the interactions with an application's
AM container. AMLauncher should also replace the raw ContainerManager proxy with NMClient.

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

View raw message