Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WorkerLostError Handling #408

Open
Santifire92 opened this issue Aug 8, 2024 · 0 comments
Open

WorkerLostError Handling #408

Santifire92 opened this issue Aug 8, 2024 · 0 comments

Comments

@Santifire92
Copy link

Santifire92 commented Aug 8, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant