[
https://issues.apache.org/jira/browse/YARN-8453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915818#comment-16915818
]
Zhankun Tang commented on YARN-8453:
------------------------------------
Bulk update: Preparing for 3.1.3 release. moved all 3.1.3 non-blocker issues to
3.1.4, please move back if it is a blocker for you.
> 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: Major
> 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
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
