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 "Wangda Tan (Jira)" <ji...@apache.org> on 2020/02/27 00:52:00 UTC

[jira] [Created] (YARN-10169) Mixed absolute resource value and percentage-based resource value in CapacityScheduler should fail

Wangda Tan created YARN-10169:
---------------------------------

             Summary: Mixed absolute resource value and percentage-based resource value in CapacityScheduler should fail
                 Key: YARN-10169
                 URL: https://issues.apache.org/jira/browse/YARN-10169
             Project: Hadoop YARN
          Issue Type: Bug
            Reporter: Wangda Tan


To me this is a bug: if there's a queue has capacity set to float, and maximum-capacity set to absolute value. Existing logic allows the behavior.

For example:
{code:java}
queue.capacity = 0.8 
queue.maximum-capacity = [mem=x, vcore=y] {code}
We should throw exception when configured like this.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org