hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-422) Add AM-NM client library
Date Tue, 23 Apr 2013 21:37:17 GMT

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

Bikas Saha commented on YARN-422:

I was hoping that the final AMNMClient library would be a one stop library for AM's to communicate
with all the NM's in the cluster. The document outlines a wrapper around the NMProtocol for
talking to 1 NM. This wrapper is useful by itself because it hides the PBImpl etc implementation
details of the protocol itself, similar to how YarnClient started off as. AMRMClient does
a little bit more than simply wrapping the Java protocol.
So as a first step the above design for wrapping the boiler plate code of the NM Protocol
into a utility library wrapper sounds good. I think the method calls are all blocking since
the RPC itself is blocking and this is a simple wrapper around the RPC. Maybe we can call
be NMClient.

Once this is done we can look at creating an AMNMClient library that will provide a single
object that an AM can use to manage its containers. This may have its own internal threading
etc which will allow the AM to make non-blocking calls. Lets figure that out in a subsequent
jira and use this one to just write the wrapper NMCLient that you have proposed.
> 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: 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

View raw message