hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7739) DefaultAMSProcessor should properly check customized resource types against minimum/maximum allocation
Date Tue, 30 Jan 2018 14:39:00 GMT

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

Sunil G commented on YARN-7739:
-------------------------------

This change looks fine to me. Since ResourceUtils ensures the normalization of resource units
while creating Resource object, we dont need to do convert as well.

+1 from me. I could commit patch tomorrow if no objections

> DefaultAMSProcessor should properly check customized resource types against minimum/maximum
allocation
> ------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-7739
>                 URL: https://issues.apache.org/jira/browse/YARN-7739
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>            Priority: Blocker
>         Attachments: YARN-7739.001.patch
>
>
> Currently, YARN RM reject requested resource if memory or vcores are less than 0 or greater
than maximum allocation. We should run the check for customized resource types as well.



--
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