[jira] [Commented] (FLINK-19556) YarnResourceManagerDriver.getPendingRequestsAndCheckConsistency only returns container requests for first matching equivalent resource

["Yangze Guo (Jira)" <ji...@apache.org>]

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

Yangze Guo commented on FLINK-19556:
------------------------------------

Supplement: [discussion thread|https://github.com/apache/flink/pull/13311#discussion_r500132158].

I think this issue is related to FLINK-19324. If we decide to go back to the priority-based design, this issue would be naturally fixed as well.

cc [~xintongsong]

> YarnResourceManagerDriver.getPendingRequestsAndCheckConsistency only returns container requests for first matching equivalent resource
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-19556
>                 URL: https://issues.apache.org/jira/browse/FLINK-19556
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / YARN
>    Affects Versions: 1.12.0
>            Reporter: Till Rohrmann
>            Priority: Major
>             Fix For: 1.12.0
>
>
> The {{YarnResourceManagerDriver}} will retrieve the number of pending container requests for a given {{Resource}} by calling {{YarnResourceManagerDriver.getPendingRequestsAndCheckConsistency(Resource)}}. Part of this method is to find the equivalent resources for the given resource. Next we find for every equivalent resource the matching container requests. Instead of unifying these collection of container requests, the method returns the first non-empty collection. This might return an incomplete set of container requests if the Yarn respects the vcores of resources given to {{AMRMClientAsync.getMatchingRequests}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)