You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Chaoran Yu (Jira)" <ji...@apache.org> on 2022/04/07 00:49:00 UTC
[jira] [Created] (YUNIKORN-1173) Basic scheduling fails on an existing cluster
Chaoran Yu created YUNIKORN-1173:
------------------------------------
Summary: Basic scheduling fails on an existing cluster
Key: YUNIKORN-1173
URL: https://issues.apache.org/jira/browse/YUNIKORN-1173
Project: Apache YuniKorn
Issue Type: Bug
Components: shim - kubernetes
Reporter: Chaoran Yu
Attachments: logs.txt, statedump.txt
Environment: EKS K8s 1.20.
K8shim built based on commit: [https://github.com/apache/yunikorn-k8shim/commit/be3bb70d9757b27d0c40d446306b928c79c80a9f]
Core version used: v0.0.0-20220325135453-73d55282f052
After YuniKorn is deployed, I deleted one of the pods managed by K8s deployment, but YK didn't schedule the new pod that's created:
*spo-og60-03-spark-operator-86cc7ff747-9vzxl*
is the name of the new pod. It's stuck in pending and its event said "spark-operator/spo-og60-03-spark-operator-86cc7ff747-9vzxl is queued and waiting for allocation"
State dump and scheduler logs are attached
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org