Check for impossible to execute tasks #99392
Labels
No Label
Good First Issue
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Job Type
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: studio/flamenco#99392
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @dr.sybren
Added subscriber: @Sergey
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! :)