[
https://issues.apache.org/jira/browse/YARN-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhijie Shen updated YARN-422:
-----------------------------
Attachment: AMNMClient_Definition_Updated_With_Tests.txt
I've updated the definition of AMNMClient, fixing the minor bugs, synchronizing
NMCommunicator setter/getter and drafting the javadoc.
In addition, I've added the test to demonstrate how AMNMClientImpl work with
AMRMClientImpl together on YarnMiniCluster. And I've added the test for
AMNMClientAsync.
The remaining stuff in this ticket could be using AMNMClient in AMLauncher.
There're two concerns:
1. Semantically, it is a bit strange RM use "AM"NMClient.
2. Technically, hadoop-yarn-client has dependency on
hadoop-yarn-server-resourcemanager in test scope. If we want to use AMNMClient
in AMLauncher, hadoop-yarn-server-resourcemanager needs to add the dependency
on hadoop-yarn-client, forming a circular dependency.
> Add AM-NM client library
> ------------------------
>
> Key: YARN-422
> URL: https://issues.apache.org/jira/browse/YARN-422
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Zhijie Shen
> Attachments: AMNMClient_Defination.txt,
> AMNMClient_Definition_Updated_With_Tests.txt, proposal_v1.pdf
>
>
> Create a simple wrapper over the AM-NM container protocol to provide hide the
> details of the protocol implementation.
--
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
