[
https://issues.apache.org/jira/browse/YARN-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653177#comment-13653177
]
Bikas Saha commented on YARN-660:
---------------------------------
As outlined in the comments on YARN-103, there were plans to add cookies in
ContainerRequest to enable schedulers to save information about the request
when they make a container request. This reduces developer burden. Common
example is to save information about which task this request was made for so
that when a received container matches the request then the task info can be
readily obtained without having to maintain duplicate maps at the user level.
Also, it would be helpful if the AMRMClient allowed users to look up its own
requests that match a set of criteria. This can be used to find out which
request to assign a new container to. The user could again maintain their own
maps but they may diverge in logic from what the AMRMClient actually translates
them to. So if the AMRMClient had a getMatchingRequests method then it could be
used as a single source of truth.
The patch provides these changes as well as fixes some bugs/minor improvements
in error handling to AMRMClientAsync. The changes are backed by real use case
scenarios used in the development of the scheduler for the
[TEZ|https://issues.apache.org/jira/browse/TEZ] application master.
> Improve AMRMClient with cookies and matching requests
> -----------------------------------------------------
>
> Key: YARN-660
> URL: https://issues.apache.org/jira/browse/YARN-660
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Attachments: YARN-660.1.patch
>
>
--
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
