Ayub Pathan created YUNIKORN-521:
------------------------------------
Summary: Placeholder pods are not cleaned up even when the job is
deleted
Key: YUNIKORN-521
URL: https://issues.apache.org/jira/browse/YUNIKORN-521
Project: Apache YuniKorn
Issue Type: Bug
Components: core - scheduler
Reporter: Ayub Pathan
Fix For: 0.10
Attachments: job.yaml, ns.yaml
This one is a negative test...
* Create a namespace with quota
* Submit a job where the placeholder pods resource requests are more than queue
quota.
* Delete the job using kubectl
* Still the placeholder pods are in running state occupying the resources.
>From an end user perspective, each job is an application consisting of all
>related pods. If the user decides to purge the job, Yunikorn should also
>recognize this action and clean up the placeholder pods.
>From a yunikorn point of view, the application and job are 2 different
>entities. The placeholder pods are not cleaned up because the application is
>still alive even though the job is deleted. Does it make sense to create a one
>on one mapping for job and application? Once the lifecycle of job is complete,
>application should also terminate in Yunikorn world. Let me know your thoughts.
--
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
