[
https://issues.apache.org/jira/browse/YUNIKORN-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17093190#comment-17093190
]
Kinga Marton commented on YUNIKORN-93:
--------------------------------------
[~wwei], below you can find my answers to your observations:
{quote}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}
I think doesn't make sense to have a queue having 0 for all capacities, that
queue would be unusable. However I can think about one scenario: what about is
a user wants to make a queue temporally unavailable, would that make sense to
set all the capacities to 0 instead of deleting and then recreating it?
{quote}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.
{quote}
I am not very familiar with the internals yet. Missing the reservations seemed
a valid thing for me. [~wilfreds] what do you think about this?
bq. apart from these, how we handle the unlimited case?
The unlimited case should not be equal to 0. We should set "N/A" or something
with the meaning of not set or not available. I created a subtask for this
because it seems that the webapp is setting it to 0 even if in the core I set
N/A or empty String. See YUNIKORN-113
> 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]
