hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-641) Make AMLauncher in RM Use NMClient
Date Thu, 06 Jun 2013 18:51:20 GMT

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

Zhijie Shen commented on YARN-641:

One blocking issue here is that if AMLauncher want to refer NMClient, resourcemanager sub-project
needs to add dependency on yarn-client. On the other hand, yarn-client already has the dependency
on resourcemanager for the test phase. It seems that the cyclic dependency error will be reported
no matter what the phase of the dependency is. Correct me if I am wrong.

IMHO, the way to walk around could be refactoring the code: either moving NMClient set to
hadoop-common or moving test classes to their related server sub-projects and eliminating
yarn-client's dependency on server sub-projects. Any suggestion?
> 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