Check for impossible to execute tasks #99392

Open
opened 2022-07-04 14:27:56 +02:00 by Sybren A. Stüvel · 5 comments

At Manager startup, it should check for impossible to execute tasks.

For example, consider the scenario where all but one worker were blocklisted for a certain task type, and the last worker that could run it, failed it. Now if that failure was that Worker's first one, it would not get blocklisted and still counts as "can execute this task type on this job". However, since it failed the task, it won't be allowed to retry it, and thus the task will get stuck in soft-failed status.

This could be implemented on the persistence layer, by breaking up the task scheduler function into several parts, which then can be called by both the task scheduler and the "unfinishable jobs" checker.


After this is implemented, it could be interesting to run this as a background goroutine every once in a while.

At Manager startup, it should check for impossible to execute tasks. For example, consider the scenario where all but one worker were blocklisted for a certain task type, and the last worker that could run it, failed it. Now if that failure was that Worker's first one, it would *not* get blocklisted and still counts as "can execute this task type on this job". However, since it failed the task, it won't be allowed to retry it, and thus the task will get stuck in `soft-failed` status. This could be implemented on the persistence layer, by breaking up the task scheduler function into several parts, which then can be called by both the task scheduler and the "unfinishable jobs" checker. --------------- After this is implemented, it could be interesting to run this as a background goroutine every once in a while.
Author
Owner

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Author
Owner

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren
Author
Owner

Added subscriber: @Sergey

Added subscriber: @Sergey
Author
Owner

Maybe @Sergey is interested in this?
Just kidding, just @mentioning him here for the Gitea migration testing.

Maybe @Sergey is interested in this? Just kidding, just @mentioning him here for the Gitea migration testing.

@dr.sybren I am all up for the impossible tasks! :)

@dr.sybren I am all up for the impossible tasks! :)
Sybren A. Stüvel added
Type
To Do
and removed
Type
Report
labels 2023-02-17 11:17:03 +01:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: studio/flamenco#99392
No description provided.