[jira] [Resolved] (YUNIKORN-1083) Doc step for deploying admission controller in manual process
[ https://issues.apache.org/jira/browse/YUNIKORN-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anuraag Nalluri resolved YUNIKORN-1083. --- Resolution: Fixed > Doc step for deploying admission controller in manual process > - > > Key: YUNIKORN-1083 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1083 > Project: Apache YuniKorn > Issue Type: Task > Components: documentation >Reporter: Anuraag Nalluri >Assignee: Anuraag Nalluri >Priority: Minor > Labels: pull-request-available > > We don't currently have documentation for deploying the admission controller > in the [manual > process|https://yunikorn.apache.org/docs/0.12.1/developer_guide/deployment/]. > We need to add this step so this process has parity with deploying YK via > helm. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-1083) Doc step for deploying admission controller in manual process
Anuraag Nalluri created YUNIKORN-1083: - Summary: Doc step for deploying admission controller in manual process Key: YUNIKORN-1083 URL: https://issues.apache.org/jira/browse/YUNIKORN-1083 Project: Apache YuniKorn Issue Type: Task Components: documentation Reporter: Anuraag Nalluri Assignee: Anuraag Nalluri We don't currently have documentation for deploying the admission controller in the [manual process|https://yunikorn.apache.org/docs/0.12.1/developer_guide/deployment/]. We need to add this step so this process has parity with deploying YK via helm. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-946) Accounting resources for deleted executor pods
[
https://issues.apache.org/jira/browse/YUNIKORN-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anuraag Nalluri resolved YUNIKORN-946.
--
Resolution: Fixed
> Accounting resources for deleted executor pods
> --
>
> Key: YUNIKORN-946
> URL: https://issues.apache.org/jira/browse/YUNIKORN-946
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: core - scheduler
>Affects Versions: 0.11
>Reporter: Ashutosh Singh
>Assignee: Anuraag Nalluri
>Priority: Critical
> Attachments: after-yunikorn-776.png, before-yunikorn-776.png,
> image-2021-11-16-23-17-42-819.png, image-2021-11-16-23-18-28-349.png
>
>
> Even when executors are deleted, YK UI shows that resources are consumed by
> the pod (the one which is already deleted). _kubectl get pods_ does not show
> the executor but YK UI shows the information of a deleted pod consuming
> resources even after few hours.
> It results into leaking cluster resources.
> Steps:
> # Run a spark application using k8s spark operator
> # Wait for executors to be in running state.
> # Delete the application using `kubectl delete sparkapplications `
> OR `kubectl delete {-}{{-}}f `
> # All the driver and executor pods would be deleted. check `kubectl get pods`
> # However, YK UI still shows some of the executors running and consuming
> resources. It leads to leak of the resource as they are considered as used
> and could not be used by pending pods.
> More details:
> [https://yunikornworkspace.slack.com/archives/CLNUW68MU/p1637126093006900]
> !image-2021-11-16-23-18-28-349.png|width=534,height=323!
>
> !image-2021-11-16-23-17-42-819.png|width=583,height=353!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-1069) Make the state dump file's log rotation parameters configurable
Anuraag Nalluri created YUNIKORN-1069: - Summary: Make the state dump file's log rotation parameters configurable Key: YUNIKORN-1069 URL: https://issues.apache.org/jira/browse/YUNIKORN-1069 Project: Apache YuniKorn Issue Type: Task Reporter: Anuraag Nalluri We need to make the state dump file's log rotation parameters (max file size, # of backups) configurable. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-1068) Doc changes for YUNIKORN-949
Anuraag Nalluri created YUNIKORN-1068: - Summary: Doc changes for YUNIKORN-949 Key: YUNIKORN-1068 URL: https://issues.apache.org/jira/browse/YUNIKORN-1068 Project: Apache YuniKorn Issue Type: Task Reporter: Anuraag Nalluri Assignee: Anuraag Nalluri Need to document changes for YUNIKORN-949. Specifically, we need to document the new partition-level config that can be set to change the output location of periodic state dump. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-1030) Delay in UI "Application History" graph for running applications
Anuraag Nalluri created YUNIKORN-1030: - Summary: Delay in UI "Application History" graph for running applications Key: YUNIKORN-1030 URL: https://issues.apache.org/jira/browse/YUNIKORN-1030 Project: Apache YuniKorn Issue Type: Bug Components: webapp Reporter: Anuraag Nalluri Fix For: 1.0.0 Attachments: Screen Shot 2022-01-13 at 6.59.04 PM.png "Application History" graph in the Yunikorn UI has approximately 4-5 min. delay in displaying running applications compared to the "Container History" graph. Configuration used is in queues.yaml specified [here|https://yunikorn.apache.org/docs/0.8.0/setup/deployment#create-the-configmap]. Slack conversation is [here|https://yunikornworkspace.slack.com/archives/CLNUW68MU/p1641612673012600]. Deploy the example sleep job (3 applications) with the above queues.yaml configuration to reproduce. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-995) Helm installation of Yunikorn fails on Kubernetes 1.22
Anuraag Nalluri created YUNIKORN-995:
Summary: Helm installation of Yunikorn fails on Kubernetes 1.22
Key: YUNIKORN-995
URL: https://issues.apache.org/jira/browse/YUNIKORN-995
Project: Apache YuniKorn
Issue Type: Bug
Reporter: Anuraag Nalluri
Here's the following kubernetes client/server info on my local machine:
{code:java}
➜ incubator-yunikorn-k8shim git:(master) ✗ kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4",
GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"clean",
BuildDate:"2021-11-17T15:48:33Z", GoVersion:"go1.16.10", Compiler:"gc",
Platform:"darwin/arm64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4",
GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"clean",
BuildDate:"2021-11-17T15:42:41Z", GoVersion:"go1.16.10", Compiler:"gc",
Platform:"linux/arm64"} {code}
This results in the following error when running the `helm install` command
from the docs:
{code:java}
➜ incubator-yunikorn-k8shim git:(master) ✗ helm install yunikorn
yunikorn/yunikorn --namespace yunikornError: INSTALLATION FAILED: failed
pre-install: unable to build kubernetes object for deleting hook
yunikorn/templates/rbac.yaml: unable to recognize "": no matches for kind
"ClusterRoleBinding" in version "rbac.authorization.k8s.io/v1beta1"{code}
I believe this is because `ClusterRoleBinding` is removed from
`rbac.authorization.k8s.io/v1beta1` as of version 1.22 of Kubernetes. We should
instead use the following `apiVersion` for this resource in the yaml:
`rbac.authorization.k8s.io/v1`.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
