[
https://issues.apache.org/jira/browse/YUNIKORN-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17945488#comment-17945488
]
Mit Desai edited comment on YUNIKORN-2772 at 4/17/25 6:41 PM:
--------------------------------------------------------------
Reproducing this was simple.
I ran a sample sleep job. Then deleted the scheduler pod. Once the scheduler
came back up, the application submit time was changed and set close to the
scheduler start time.
was (Author: mitdesai):
Reproducing this was simple.
I ran a sample sleep job. Then deleted the scheduler pod. Once the scheduler
came back up, the application submit time was changed and set close to the
scheduler start time.
> 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
>
> Attachments: Screenshot 2025-04-14 at 5.47.47 PM.png, Screenshot
> 2025-04-14 at 5.57.31 PM.png
>
>
> 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-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
