[
https://issues.apache.org/jira/browse/YARN-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15433742#comment-15433742
]
Arun Suresh commented on YARN-4889:
-----------------------------------
I totally agree with you... But since currently, the AMRMClient does not remove
outstanding ContainerRequests automatically (user is required to call
_getMatchingRequests_ plugging in the properties of the returned container. The
user is then required to call _removeContainerRequest_ using the result of the
_getMatchingRequests_ call).
Once we remove outstanding ContainerRequests automatically, we can as you say,
do away with the _getMatchingRequests_ altogether.
> Changes in AMRMClient for identifying resource-requests explicitly
> ------------------------------------------------------------------
>
> Key: YARN-4889
> URL: https://issues.apache.org/jira/browse/YARN-4889
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Subru Krishnan
> Assignee: Arun Suresh
> Attachments: YARN-4889.001.patch, YARN-4889.002.patch,
> YARN-4889.003.patch, YARN-4889.004.patch
>
>
> YARN-4879 proposes the notion of identifying allocate requests explicitly..
> This JIRA is to track the changes in AMRMClient to keep it wire compatible
> with the changes. Please refer to the design doc in the parent JIRA for
> details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
