Skip to content

tasks should be rerun sooner when the machine they're running on is known to be gone #7472

@bhearsum

Description

@bhearsum

While digging into some worker issues today I noticed an odd state: a worker was known to be shutdown, but the task was still marked as running. Eventually, the task was marked as claim expired, and rerun. But this begs the question: why can't we do that sooner if the machine that claimed it has already been killed? I assume this is because worker manager knows the latter, while the queue doesn't, but I haven't dug deeply!

Image

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions