[jira] [Assigned] (YUNIKORN-42) Better to support POD events for YuniKorn to troubleshoot allocation failures
[ https://issues.apache.org/jira/browse/YUNIKORN-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang reassigned YUNIKORN-42: --- Assignee: Adam Antal > Better to support POD events for YuniKorn to troubleshoot allocation failures > - > > Key: YUNIKORN-42 > URL: https://issues.apache.org/jira/browse/YUNIKORN-42 > Project: Apache YuniKorn > Issue Type: Task >Reporter: Wangda Tan >Assignee: Adam Antal >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Now it is tricky to do troubleshoot for pod allocation, we need better expose > this information to POD description. -- 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
[jira] [Updated] (YUNIKORN-110) Configured queue capacity should not exceed configured max capacity
[ https://issues.apache.org/jira/browse/YUNIKORN-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton updated YUNIKORN-110: -- Attachment: Screenshot 2020-04-23 at 16.24.13.png > 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 >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
[jira] [Created] (YUNIKORN-110) Configured queue capacity should not exceed configured max capacity
Kinga Marton created YUNIKORN-110: - Summary: 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 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
[jira] [Updated] (YUNIKORN-93) Queue maximum capacity cleanup
[ https://issues.apache.org/jira/browse/YUNIKORN-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton updated YUNIKORN-93: - Summary: Queue maximum capacity cleanup (was: Provide queue absolute used capacity in rest API) > 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: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-66) Add labels to the history view on the web UI
[ https://issues.apache.org/jira/browse/YUNIKORN-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB resolved YUNIKORN-66. -- Fix Version/s: 0.9 Resolution: Fixed > Add labels to the history view on the web UI > > > Key: YUNIKORN-66 > URL: https://issues.apache.org/jira/browse/YUNIKORN-66 > Project: Apache YuniKorn > Issue Type: Improvement > Components: webapp >Reporter: Wilfred Spiegelenburg >Assignee: Akhil PB >Priority: Minor > Fix For: 0.9 > > > The backend will return the running applications and or containers. The page > does not really make that clear, a label or mouse hover should explain what > is displayed. > In the future, can we include total ones, and completed ones in this chart > too if possible? -- 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
