You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Sunil Govindan (JIRA)" <ji...@apache.org> on 2018/06/27 19:53:00 UTC
[jira] [Commented] (YARN-8453) Additional Unit tests to verify
queue limit and max-limit with multiple resource types
[ https://issues.apache.org/jira/browse/YARN-8453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16525522#comment-16525522 ]
Sunil Govindan commented on YARN-8453:
--------------------------------------
[~leftnoteasy] , cud u pls help to check this.
> Additional Unit tests to verify queue limit and max-limit with multiple resource types
> ---------------------------------------------------------------------------------------
>
> Key: YARN-8453
> URL: https://issues.apache.org/jira/browse/YARN-8453
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler
> Affects Versions: 3.0.2
> Reporter: Sunil Govindan
> Assignee: Sunil Govindan
> Priority: Blocker
> Attachments: YARN-8453.001.patch
>
>
> Post support of additional resource types other then CPU and Memory, it could be possible that one such new resource is exhausted its quota on a given queue. But other resources such as Memory / CPU is still there beyond its guaranteed limit (under max-limit). Adding more units test to ensure we are not starving such allocation requests
--
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