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

worker signals and solo concurrency #6073

Open
neg3ntropy opened this issue May 4, 2020 · 5 comments
Open

worker signals and solo concurrency #6073

neg3ntropy opened this issue May 4, 2020 · 5 comments

Comments

@neg3ntropy
Copy link

neg3ntropy commented May 4, 2020

4.4.0

worker_process_shutdown signal is not sent when a task is running with the solo pool. The solo pool is great for debugging, but it my case it makes the process hard to kill.

This is basically a rehash of #5405, but for another signal. It might make sense to generalize the solution to other relevant signals if any.

PS: Furthermore, it looks that the running task is left to finish and then the ACK fails, so it gets retried later.

@auvipy
Copy link
Member

auvipy commented May 5, 2020

can you send a PR with fix and unit tests?

@neg3ntropy
Copy link
Author

At least in the immediate future, no sorry, otherwise I would have done it.

@auvipy
Copy link
Member

auvipy commented May 5, 2020

are you using the latest version of celery? and can you try celery from Github master?

@neg3ntropy
Copy link
Author

still present in master

@auvipy
Copy link
Member

auvipy commented May 5, 2020

please provide a failing testcase

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