hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weiwei Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-8984) OutstandingSchedRequests in AMRMClient could not be removed when AllocationTags is null or empty
Date Wed, 07 Nov 2018 04:34:00 GMT

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

Weiwei Yang commented on YARN-8984:
-----------------------------------

Thanks [~fly_in_gis] for creating this issue, I have increased the priority to critical.

The patch looks good to me, one nit is instead of adding a new class \{{TestAMRMClientOutstandingSchedulingRequest}},
can we move this test case to \{{TestAMRMClientPlacementConstraints}}?

Cc [~botong], [~asuresh].

 

> OutstandingSchedRequests in AMRMClient could not be removed 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
>
>
> 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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message