[
https://issues.apache.org/jira/browse/YARN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538364#comment-13538364
]
Bikas Saha commented on YARN-103:
---------------------------------
Looks like there are different views on interface usage. How about the
following proposal?
The next step after this gets committed is to write a version of the AMRMClient
that is more advanced and handles things like auto-heartbeat and
task->container matching. This will be useful for simple applications that dont
need fine grained control over scheduling. After I am done writing that client
then it will be clear if the interface API's apply or if its better to write
that class with a different API. Based on that we can continue to keep the
interface and add a factory or remove the interface. Does this sound like a way
forward?
> 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, YARN-103.4.wrapper.patch, YARN-103.5.patch,
> YARN-103.6.patch, YARN-103.7.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
