You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2025/04/17 00:09:00 UTC
[jira] [Reopened] (YUNIKORN-2772) Scheduler restart does not preserve app start time
[ https://issues.apache.org/jira/browse/YUNIKORN-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wilfred Spiegelenburg reopened YUNIKORN-2772:
---------------------------------------------
After discussion in the community sync we have found a gap: pending allocations change the time but already allocated pods do not.
There is a second path in the code that needs the change for the create time in {{addAllocationInternal()}}
Reopening the Jira to add the second path
> Scheduler restart does not preserve app start time
> --------------------------------------------------
>
> Key: YUNIKORN-2772
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2772
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
> Reporter: Mit Desai
> Assignee: Peter Bacsko
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.7.0
>
>
> Whenever the scheduler is restarted, all the applications create time is set to the current time, ignoring the original value that comes from the API server.
> Due to this, FIFO sorting can show irregularity in scheduling.
> If there is an App1 that started 2 days ago and App2 that started 1 day ago, during scheduler restart, both the apps will get almost same created time (nano seconds apart). App2 create time can be just a few nano seconds ahead of App1 and hence App2 gets priority over App1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org