Skip to content

WorkerLostError Handling #408

@Santifire92

Description

@Santifire92

Hi, @auvipy !
I have a question, how can we handle this scenario where a worker gets lost abruptly like with a sigkill?
In the case of a timout i see you raise the exception so it gets propagated upwards but whit the worker lost it just gets catched and passes as nothing happened to the upper coordinator.

Can this be raised/what can i do?

billiard/billiard/pool.py

Lines 1263 to 1273 in 81cc942

def mark_as_worker_lost(self, job, exitcode):
try:
raise WorkerLostError(
'Worker exited prematurely: {0} Job: {1}.'.format(
human_status(exitcode), job._job),
)
except WorkerLostError:
job._set(None, (False, ExceptionInfo()))
else: # pragma: no cover
pass

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions