Skip to content
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.

P0.5: Watchdog auto delete leak priorityclass #3866

Closed
yqwang-ms opened this issue Nov 19, 2019 · 0 comments
Closed

P0.5: Watchdog auto delete leak priorityclass #3866

yqwang-ms opened this issue Nov 19, 2019 · 0 comments
Assignees

Comments

@yqwang-ms
Copy link
Member

yqwang-ms commented Nov 19, 2019

Short summary about the issue/question:
Even after #3808 (comment), framework cannot be foreground deleted sometimes. (Behaivor changed for new version see #4117)
So, we should not continue to cross-namespace owner references anymore (even if blockOwnerDeletion=false), since it is disallowed by design.

So, in short term, we can periodically check if a priorityclass still has its corresponding framework, if not, watchdog should treat it as leak, and delete it automatically.

BTW, remove the owner references in RestServer, and delete all priorityclass when delete the FC.

In long term, we should customize queuing order by scheduler framework, instead of per job priority class object.

@yqwang-ms yqwang-ms changed the title Watchdog auto delete leak priorityclass P0.5: Watchdog auto delete leak priorityclass Jan 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants