[
https://issues.apache.org/jira/browse/YARN-8984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16678081#comment-16678081
]
Yang Wang commented on YARN-8984:
---------------------------------
There's no difference between in a separate class and in
TestAMRMClientPlacementConstraints.
When set YarnConfiguration.RM_PLACEMENT_CONSTRAINTS_HANDLER to scheduler, we
could not get rejectedSchedulingRequests from AllocateResponse. It is not set
by the capacity scheduler. So i add another test in
TestAMRMClientPlacementConstraints.
[~cheersyang] Please help to review.
> AMRMClient#OutstandingSchedRequests leaks when AllocationTags is null or empty
> ------------------------------------------------------------------------------
>
> Key: YARN-8984
> URL: https://issues.apache.org/jira/browse/YARN-8984
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Yang Wang
> Assignee: Yang Wang
> Priority: Critical
> Attachments: YARN-8984-001.patch, YARN-8984-002.patch
>
>
> In AMRMClient, outstandingSchedRequests should be removed or decreased when
> container allocated. However, it could not work when allocation tag is null
> or empty.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
