You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Zhijie Shen (JIRA)" <ji...@apache.org> on 2013/05/01 09:42:16 UTC

[jira] [Updated] (YARN-422) Add AM-NM client library

     [ https://issues.apache.org/jira/browse/YARN-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhijie Shen updated YARN-422:
-----------------------------

    Attachment: YARN-422.1.patch

Here's the first patch, which is ready for review. Based on the previous definition file, the patch has the following updates:

1. Refactor some code (add some more logs, paraphrase the javadoc, and etc)

2. Rename AMNMClient to NMClient since not only AM will use this client.

3. In NMClientAsync, join the threadpool's thread, which is set to non-daeomon.

4. Enhance the test cases.

As the patch is already big, I suggest to defer the code changes of using the client in AM and RM in the follow-up patches. In addition, as I found, maven seems not to distinguish scope when checking cyclic dependency. Therefore, making resourcemanager project depend on client (to use NMClient in AMLauncher) will fail the build.
                
> 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, YARN-422.1.patch
>
>
> 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