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-103) Add a yarn AM - RM client module
Date Sun, 07 Oct 2012 22:26:03 GMT

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

Bikas Saha commented on YARN-103:

- Changed to addResourceRequest.
- Changed javadoc.
- This client is the barebones implementation and hence has no smarts. The checks can be implemented/may
not be necessary in smarter versions of the client. Additionally, like you say, some information
may be better exposed at different API's.
- I actually want to test against the MiniMRCluster instead of an expected behavior via a
mockRM. I want the client test to fail if the RM  behavior changes. So yes this is more of
a functional test than a unit test.
- Used BuilderUtils where available
- I prefer not to do addAll because the current code explains the logic better and is resilient
to the way comparators for the set object work.
> Add a yarn AM - RM client module
> --------------------------------
>                 Key: YARN-103
>                 URL: https://issues.apache.org/jira/browse/YARN-103
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>         Attachments: YARN-103.1.patch, YARN-103.2.patch, YARN-103.3.patch, YARN-103.4.patch
> Add a basic client wrapper library to the AM RM protocol in order to prevent proliferation
of code being duplicated everywhere. Provide helper functions to perform reverse mapping of
container requests to RM allocation resource request table format.

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