[
https://issues.apache.org/jira/browse/YUNIKORN-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17102630#comment-17102630
]
Kinga Marton edited comment on YUNIKORN-110 at 5/8/20, 3:02 PM:
----------------------------------------------------------------
It seems that hierarchy check is already performed in the
[initializer|[https://github.com/apache/incubator-yunikorn-core/blob/master/pkg/cache/initializer.go#L171]].
Actually both checks are performed in the initializer, but as [~wilfreds]
mentioned the root is skipped. So I am going to close this issue.
was (Author: kmarton):
It seems that hierarchy check is already performed in the
[initializer|[https://github.com/apache/incubator-yunikorn-core/blob/master/pkg/cache/initializer.go#L171]].
> Configured queue capacity should not exceed configured max capacity
> -------------------------------------------------------------------
>
> Key: YUNIKORN-110
> URL: https://issues.apache.org/jira/browse/YUNIKORN-110
> Project: Apache YuniKorn
> Issue Type: Bug
> Reporter: Kinga Marton
> Assignee: Kinga Marton
> Priority: Major
> Attachments: Screenshot 2020-04-23 at 16.24.13.png
>
>
> When running some examples I saw in the UI that the configured capacity was
> higher than the configured max capacity for the root queue.
> I think this has no sense, since the max capacity for the root queue is the
> same as the cluster capacity, an it is a hard limit, so having higher value
> makes no sense.
> As the documentation says there should be no guaranteed resource set for the
> root queue:
> https://github.com/apache/incubator-yunikorn-core/blob/master/docs/queue_config.md
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
