[
https://issues.apache.org/jira/browse/YUNIKORN-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko updated YUNIKORN-2977:
-----------------------------------
Description:
We identified a couple of issues with DaemonSet preemption. The current
implementation is not stable.
Notable issues:
1. Flooding the logs from {{tryAllocate()}} because unreservation fails
2. Flooding the logs if there are no victims found
3. Allocation is stuck if the DS pod cannot run on the target node due to
predicate errors.
was:
We identified a couple of issues with DaemonSet preemption. The current
implementation it's not stable.
Notable issues:
1. Flooding the logs from {{tryAllocate()}} because unreservation fails
2. Flooding the logs if there are no victims found
3. Allocation is stuck if the DS pod cannot run on the target node due to
predicate errors.
> [Umbrell] DaemonSet preemption hardening
> ----------------------------------------
>
> Key: YUNIKORN-2977
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2977
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: core - scheduler
> Reporter: Peter Bacsko
> Priority: Major
>
> We identified a couple of issues with DaemonSet preemption. The current
> implementation is not stable.
> Notable issues:
> 1. Flooding the logs from {{tryAllocate()}} because unreservation fails
> 2. Flooding the logs if there are no victims found
> 3. Allocation is stuck if the DS pod cannot run on the target node due to
> predicate errors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
