[
https://issues.apache.org/jira/browse/YUNIKORN-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17090945#comment-17090945
]
Weiwei Yang commented on YUNIKORN-93:
-------------------------------------
{quote}
0 value does make sense since this means that the specified resource is not
available for the queue
{quote}
this is correct. But what I meant to say was the capacity is 0, which means all
values for different resource types are all 0. is that also a valid case?
should we allow that?
{quote}
we should parse the info from the scheduler package instead of parsing it from
the cache, since the scheduler has more information for example it has
information on the reservation
{quote}
I doubt this point. Cache should be our source of truth, and UI should get info
from the cache. The scheduler package are the internal states for each
scheduling thread (in case we have more than 1 in feature). that is not
supposed to be exposed outside. Scheduler has more information, but I don't
think we need to expose all of that info via REST. A more appropriate place for
them is the event system we are going to build.
apart from these, how we handle the unlimited case?
> Queue maximum capacity cleanup
> ------------------------------
>
> Key: YUNIKORN-93
> URL: https://issues.apache.org/jira/browse/YUNIKORN-93
> Project: Apache YuniKorn
> Issue Type: Improvement
> Reporter: Kinga Marton
> Assignee: Kinga Marton
> Priority: Minor
>
> Right now the absolute used capacity is hardcoded to 20%.
> The usage bar is rendered by this value, but currently, it is hardcoded.
> Note, both capacity/max capacity could be 0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
