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

billiard.exceptions.WorkerLostError: Worker exited prematurely: exitcode 1 #370

Open
shaMiaoMiao opened this issue Oct 14, 2021 · 3 comments

Comments

@shaMiaoMiao
Copy link

shaMiaoMiao commented Oct 14, 2021

celery billiard error

I found a billiard error when use celery with version == '5.1.2' . main msg like:

Traceback (most recent call last): File "/home/work/pyenv/celery/lib/python3.7/site-packages/billiard/pool.py", line 1267, in mark_as_worker_lost human_status(exitcode), job._job), billiard.exceptions.WorkerLostError: Worker exited prematurely: exitcode 1 Job: 172.

Detail version is :

billiard == 3.6.4.0

celery == 5.1.2

And start script is :

celery multi restart secondary_work -c 30 -A metric_celery -Q secondary_queue --pidfile="$HOME/run/celery/%n.pid" --logfile="$HOME/log/celery/%n%I.log" --max-tasks-per-child=50

I use two queue on different server.

Looks like a billiard process problem and its a occasional anomaly, i try to set -c 20 and max-tasks-per-child=50, but it's helpless, i am not sure whether need to set a large num.

Does anyone has a good idea?

Thanks !

@open-collective-bot
Copy link

Hey @shaMiaoMiao 👋,
Thank you for opening an issue. We will get back to you as soon as we can.
Also, check out our Open Collective and consider backing us - every little helps!

We also offer priority support for our sponsors.
If you require immediate assistance please consider sponsoring us.

@auvipy
Copy link
Member

auvipy commented Oct 15, 2021

probably this is a billiard issue, can you try 5.2.0rc1 and report again? can you check billiard repo? i could migrate this issue there. also please share more detail about your deployment and codes according to issue template

@shaMiaoMiao
Copy link
Author

probably this is a billiard issue, can you try 5.2.0rc1 and report again? can you check billiard repo? i could migrate this issue there. also please share more detail about your deployment and codes according to issue template

Thanks for ur reply. It's useless to update celery version to 5.2.0rc1. I update codes according and some informations in issue template, looking forward to your help. Thank you very very much!

@auvipy auvipy transferred this issue from celery/celery Aug 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants