[ https://issues.apache.org/jira/browse/YUNIKORN-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865979#comment-17865979 ]
Chia-Ping Tsai commented on YUNIKORN-2757: ------------------------------------------ [~wilfreds] thanks for nice sharing. yep, you are right. We just have a discussion with kuberay guys, and the exposed headroom is good enough. I will close this jira. BTW, I have a question about `GetMaxResource`. It seems that method is used by "root" queue only, and that means we can return the current maxResource directly without finding the ComponentWiseMin. Should we file a PR to simplify it? > Consider adding new field `resolvedMaxResource` to queue dao to show the true > limit > ----------------------------------------------------------------------------------- > > Key: YUNIKORN-2757 > URL: https://issues.apache.org/jira/browse/YUNIKORN-2757 > Project: Apache YuniKorn > Issue Type: Improvement > Reporter: Chia-Ping Tsai > Priority: Major > > The true max resources of queue is based on all parents. It could be hard to > see/understand the true "max resources" of queue by human eyes if there is a > huge queue trees. > Hence, it would be nice to add the "resolved" max resources to restful APIs. > Also, our UI can leverages the field to help users to understand which max > resource will be used by this queue -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org