[jira] [Updated] (YUNIKORN-1942) [Yunikorn] Null Batch API Response when we reset ring buffer size

[ https://issues.apache.org/jira/browse/YUNIKORN-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko updated YUNIKORN-1942: --- Parent: YUNIKORN-1628 Issue Type: Sub-task (was: Bug) > [Yunikorn] Null Batch API

[jira] [Assigned] (YUNIKORN-1942) [Yunikorn] Null Batch API Response when we reset ring buffer size

[ https://issues.apache.org/jira/browse/YUNIKORN-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko reassigned YUNIKORN-1942: -- Assignee: Peter Bacsko > [Yunikorn] Null Batch API Response when we reset ring buff

[jira] [Updated] (YUNIKORN-1942) Null Batch API Response when we reset ring buffer size

[ https://issues.apache.org/jira/browse/YUNIKORN-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko updated YUNIKORN-1942: --- Summary: Null Batch API Response when we reset ring buffer size (was: [Yunikorn] Null Bat

[jira] [Created] (YUNIKORN-1942) [Yunikorn] Null Batch API Response when we reset ring buffer size

Rajesh Kanhaiya Lal created YUNIKORN-1942: - Summary: [Yunikorn] Null Batch API Response when we reset ring buffer size Key: YUNIKORN-1942 URL: https://issues.apache.org/jira/browse/YUNIKORN-1942

[jira] [Updated] (YUNIKORN-1643) Doc need to change for new limit wildcard interpretation syntax rule check.

[ https://issues.apache.org/jira/browse/YUNIKORN-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YUNIKORN-1643: - Labels: pull-request-available (was: ) > Doc need to change for new limit wildcard in

[jira] [Assigned] (YUNIKORN-1643) Doc need to change for new limit wildcard interpretation syntax rule check.

[ https://issues.apache.org/jira/browse/YUNIKORN-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikandan R reassigned YUNIKORN-1643: -- Assignee: Manikandan R (was: Qi Zhu) > Doc need to change for new limit wildcard i

[jira] [Commented] (YUNIKORN-1941) Limit Yunikorn to only use certain nodes to schedule workloads

[ https://issues.apache.org/jira/browse/YUNIKORN-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17759977#comment-17759977 ] Craig Condit commented on YUNIKORN-1941: One thing to consider when implementi

[jira] [Updated] (YUNIKORN-1941) Limit Yunikorn to only use certain nodes to schedule workloads

[ https://issues.apache.org/jira/browse/YUNIKORN-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Singer updated YUNIKORN-1941: -- Description: We want to limit Yunikorn to utilize a specific part of the Kubernetes cluster

[jira] [Updated] (YUNIKORN-1941) Limit Yunikorn to only use certain nodes to schedule workloads

[ https://issues.apache.org/jira/browse/YUNIKORN-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Singer updated YUNIKORN-1941: -- Description: We want to limit Yunikorn to utilize a specific part of the Kubernetes cluster

[jira] [Created] (YUNIKORN-1941) Limit Yunikorn to only use certain nodes to schedule workloads

Marc Singer created YUNIKORN-1941: - Summary: Limit Yunikorn to only use certain nodes to schedule workloads Key: YUNIKORN-1941 URL: https://issues.apache.org/jira/browse/YUNIKORN-1941 Project: Apache

[jira] [Commented] (YUNIKORN-1912) Upgrade golang dependencies for CVEs

[ https://issues.apache.org/jira/browse/YUNIKORN-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17759957#comment-17759957 ] Junyao Huang commented on YUNIKORN-1912: Sure. Thanks! I will go through the g

[jira] [Updated] (YUNIKORN-1933) Verify_allow_preemption_tag e2e test is flaky

[ https://issues.apache.org/jira/browse/YUNIKORN-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YUNIKORN-1933: - Labels: pull-request-available (was: ) > Verify_allow_preemption_tag e2e test is flak

[jira] [Resolved] (YUNIKORN-1920) headroom calculation fails if parent has usage and max set

[ https://issues.apache.org/jira/browse/YUNIKORN-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikandan R resolved YUNIKORN-1920. Fix Version/s: 1.4.0 Resolution: Fixed > headroom calculation fails if parent has

[yunikorn-core] branch master updated: [YUNIKORN-1920] headroom with parent queue usage (#620)

This is an automated email from the ASF dual-hosted git repository. mani pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/yunikorn-core.git The following commit(s) were added to refs/heads/master by this push: new f83134b0 [YUNIKORN-1920] headroom with pare

[jira] [Created] (YUNIKORN-1940) Remove getChildQueuePath method

Manikandan R created YUNIKORN-1940: -- Summary: Remove getChildQueuePath method Key: YUNIKORN-1940 URL: https://issues.apache.org/jira/browse/YUNIKORN-1940 Project: Apache YuniKorn Issue Type: