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 "Zhankun Tang (Jira)" <ji...@apache.org> on 2019/08/27 01:57:00 UTC
[jira] [Commented] (YARN-9785) Application gets activated even when
AM memory has reached
[ https://issues.apache.org/jira/browse/YARN-9785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916269#comment-16916269 ]
Zhankun Tang commented on YARN-9785:
------------------------------------
[~BilwaST], Thanks for reporting this. We're going to have branch cut for 3.1.3 and 3.2.1. Do you have a patch for this blocker issue? We can get it reviewed and merged soon.
> Application gets activated even when AM memory has reached
> ----------------------------------------------------------
>
> Key: YARN-9785
> URL: https://issues.apache.org/jira/browse/YARN-9785
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Bilwa S T
> Assignee: Bilwa S T
> Priority: Blocker
>
> Configure below property in resource-types.xml
> {quote}<property>
> <name>yarn.resource-types</name>
> <value>yarn.io/gpu</value>
> </property>
> {quote}
> Submit applications even after AM limit for a queue is reached. Applications get activated even after limit is reached
> !queue.png!
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org