You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@yunikorn.apache.org by "Peter Bacsko (Jira)" <ji...@apache.org> on 2025/04/14 11:47:00 UTC

[jira] [Resolved] (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 ]

Peter Bacsko resolved YUNIKORN-2772.
------------------------------------
    Fix Version/s: 1.7.0
       Resolution: Fixed

Merged to master.

> 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: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org