[jira] [Commented] (YUNIKORN-324) Add rest API to retrieve cluster resource utilization

[ https://issues.apache.org/jira/browse/YUNIKORN-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208516#comment-17208516 ] Ting Yao,Huang commented on YUNIKORN-324: - [~wwei] sure. I have upload REST API

[jira] [Commented] (YUNIKORN-323) Add a chart to display the cluster resource utilization in dashboard

[ https://issues.apache.org/jira/browse/YUNIKORN-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208514#comment-17208514 ] Ting Yao,Huang commented on YUNIKORN-323: - Hi [~akhilpb] [~wwei] , Here is the 

[jira] [Updated] (YUNIKORN-323) Add a chart to display the cluster resource utilization in dashboard

[ https://issues.apache.org/jira/browse/YUNIKORN-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ting Yao,Huang updated YUNIKORN-323: Attachment: success.json error.json > Add a chart to display the cluster

[jira] [Commented] (YUNIKORN-408) Result mismatch between Container_Status and Container_History

[ https://issues.apache.org/jira/browse/YUNIKORN-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208422#comment-17208422 ] Weiwei Yang commented on YUNIKORN-408: -- {quote} can we add change to the documenta

[jira] [Resolved] (YUNIKORN-433) Extend configwatcher expiration time in case of a new update

[ https://issues.apache.org/jira/browse/YUNIKORN-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang resolved YUNIKORN-433. -- Fix Version/s: 0.10 Resolution: Fixed > Extend configwatcher expiration time in case o

[jira] [Commented] (YUNIKORN-430) WARN and ERROR level log entries should not show a stack trace

[ https://issues.apache.org/jira/browse/YUNIKORN-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208413#comment-17208413 ] Weiwei Yang commented on YUNIKORN-430: -- Thanks [~adam.antal]. That makes sense. >

[jira] [Commented] (YUNIKORN-324) Add rest API to retrieve cluster resource utilization

[ https://issues.apache.org/jira/browse/YUNIKORN-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208325#comment-17208325 ] Weiwei Yang commented on YUNIKORN-324: -- hi [~Huang Ting Yao] one last thing for th

[jira] [Commented] (YUNIKORN-323) Add a chart to display the cluster resource utilization in dashboard

[ https://issues.apache.org/jira/browse/YUNIKORN-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208324#comment-17208324 ] Weiwei Yang commented on YUNIKORN-323: -- [~akhilpb] YUNIKORN-324 has been done, whe

[jira] [Commented] (YUNIKORN-437) Adherence to new distribution guidelines

[ https://issues.apache.org/jira/browse/YUNIKORN-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208314#comment-17208314 ] Weiwei Yang commented on YUNIKORN-437: -- Thanks for bringing this up, mark it targe

[jira] [Updated] (YUNIKORN-437) Adherence to new distribution guidelines

[ https://issues.apache.org/jira/browse/YUNIKORN-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang updated YUNIKORN-437: - Target Version: 0.10 > Adherence to new distribution guidelines > -

[jira] [Updated] (YUNIKORN-437) Adherence to new distribution guidelines

[ https://issues.apache.org/jira/browse/YUNIKORN-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang updated YUNIKORN-437: - Description: As per the new distribution guidelines mentioned in [https://incubator.apache.org/

[jira] [Commented] (YUNIKORN-429) Set default logging level to INFO

[ https://issues.apache.org/jira/browse/YUNIKORN-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208127#comment-17208127 ] Adam Antal commented on YUNIKORN-429: - Opened 2 PRs: one for the shim and one for t

[jira] [Commented] (YUNIKORN-430) WARN and ERROR level log entries should not show a stack trace

[ https://issues.apache.org/jira/browse/YUNIKORN-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208124#comment-17208124 ] Adam Antal commented on YUNIKORN-430: - Okay, thanks for the reponses. I think I clo

[jira] [Resolved] (YUNIKORN-430) WARN and ERROR level log entries should not show a stack trace

[ https://issues.apache.org/jira/browse/YUNIKORN-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Antal resolved YUNIKORN-430. - Resolution: Won't Fix > WARN and ERROR level log entries should not show a stack trace > --

[jira] [Updated] (YUNIKORN-428) Reduce the warning logs in resources.go

[ https://issues.apache.org/jira/browse/YUNIKORN-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YUNIKORN-428: Labels: pull-request-available (was: ) > Reduce the warning logs in resources.go > -

[jira] [Resolved] (YUNIKORN-324) Add rest API to retrieve cluster resource utilization

[ https://issues.apache.org/jira/browse/YUNIKORN-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-324. --- Fix Version/s: 0.10 Resolution: Fixed Thank you [~Huang Ting Yao] for working on thi

[jira] [Assigned] (YUNIKORN-352) when child queue capacity greater than parent, the configmap update is rejected but not notified to end user

[ https://issues.apache.org/jira/browse/YUNIKORN-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton reassigned YUNIKORN-352: - Assignee: Kinga Marton > when child queue capacity greater than parent, the configmap

[jira] [Commented] (YUNIKORN-435) Admission-Controller pod goes into pending state because of default serviceAccount

[ https://issues.apache.org/jira/browse/YUNIKORN-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208023#comment-17208023 ] Kinga Marton commented on YUNIKORN-435: --- [~vbm] can you please add some context t

[jira] [Resolved] (YUNIKORN-436) serviceAccount is hardcoded in rbac.yaml

[ https://issues.apache.org/jira/browse/YUNIKORN-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kinga Marton resolved YUNIKORN-436. --- Fix Version/s: 0.10 Resolution: Fixed > serviceAccount is hardcoded in rbac.yaml >

[jira] [Commented] (YUNIKORN-436) serviceAccount is hardcoded in rbac.yaml

[ https://issues.apache.org/jira/browse/YUNIKORN-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17207936#comment-17207936 ] Kinga Marton commented on YUNIKORN-436: --- Thank you [~vbm] for fixing it. I commit

[jira] [Assigned] (YUNIKORN-352) when child queue capacity greater than parent, the configmap update is rejected but not notified to end user

[ https://issues.apache.org/jira/browse/YUNIKORN-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg reassigned YUNIKORN-352: -- Assignee: (was: Wilfred Spiegelenburg) > when child queue capaci

[jira] [Updated] (YUNIKORN-308) Document the behavior of queue quota incase of hierarchical queues

[ https://issues.apache.org/jira/browse/YUNIKORN-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YUNIKORN-308: Labels: pull-request-available (was: ) > Document the behavior of queue quota incase of

[jira] [Commented] (YUNIKORN-308) Document the behavior of queue quota incase of hierarchical queues

[ https://issues.apache.org/jira/browse/YUNIKORN-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17207919#comment-17207919 ] Wilfred Spiegelenburg commented on YUNIKORN-308: Add documentation on t

[jira] [Assigned] (YUNIKORN-308) Document the behavior of queue quota incase of hierarchical queues

[ https://issues.apache.org/jira/browse/YUNIKORN-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg reassigned YUNIKORN-308: -- Assignee: Wilfred Spiegelenburg > Document the behavior of queue quo