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 "Manikandan R (Jira)" <ji...@apache.org> on 2020/02/26 17:04:00 UTC
[jira] [Commented] (YARN-9893) Capacity scheduler: enhance
leaf-queue-template capacity / maximum-capacity setting
[ https://issues.apache.org/jira/browse/YARN-9893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045707#comment-17045707 ]
Manikandan R commented on YARN-9893:
------------------------------------
[~pbacsko] Part of this requirement would be addressed in YARN-10154. We can handle support for two percentage values in separate jira.
Is that ok?
> Capacity scheduler: enhance leaf-queue-template capacity / maximum-capacity setting
> -----------------------------------------------------------------------------------
>
> Key: YARN-9893
> URL: https://issues.apache.org/jira/browse/YARN-9893
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacity scheduler
> Reporter: Peter Bacsko
> Assignee: Manikandan R
> Priority: Major
>
> Capacity Scheduler does not support two percentage values for leaf queue capacity and maximum-capacity settings. So, you can't do something like this:
> {{yarn.scheduler.capacity.root.users.john.leaf-queue-template.capacity=memory-mb=50.0%, vcores=50.0%}}
> On top of that, it's not even possible to define absolute resources:
> {{yarn.scheduler.capacity.root.users.john.leaf-queue-template.capacity=memory-mb=16384, vcores=8}}
> Only a single percentage value is accepted.
> This makes it nearly impossible to properly convert a similar setting from Fair Scheduler, where such a configuration is valid and accepted ({{<maxChildResources>}}).
--
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