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

Bug: Worker gets stuck working on a task indefinitely since 1.12.0 #442

Closed
sarnikowski opened this issue Nov 5, 2021 · 6 comments
Closed

Comments

@sarnikowski
Copy link

Issues

What OS are you using?

Ubuntu 20.04.1 LTS (Focal Fossa)

What version of Dramatiq are you using?

1.12.0

What did you do?

Enqueued jobs on a queue, on which a worker is listening.

What did you expect would happen?

That the worker does not get stuck running a task indefinitely.

What happened?

The worker gets stuck with a task running at 100% CPU, but fails to ever complete the task. I have to manually kill the process and restart it. The following warning is emitted in the logs:

[2021-11-05 12:21:37,834] [PID 8] [Thread-2] [dramatiq.brokers.redis._RedisConsumer] Found 'None' message in message cache for queue 'miner-low'. This may be a bug in dramatiq (related to #266), please report it.
@Bogdanp
Copy link
Owner

Bogdanp commented Nov 5, 2021

Would you be able to dump the contents of your queue? Either here or share it with me by e-mail. It would be really helpful to see what the data looks like.

@sarnikowski
Copy link
Author

Yes, of course. I've sent you an e-mail.

@Bogdanp
Copy link
Owner

Bogdanp commented Nov 8, 2021

Thanks again for sharing the DB! I think this is now properly fixed on master (my previous fix for this problem had the right idea, but the wrong implementation!). Please give it a try and let me know if you run into any problems.

@sarnikowski
Copy link
Author

No problem ! Thanks for the quick fix. I will let you know if the issue persists.

@mwek
Copy link

mwek commented Dec 15, 2021

Could we get a 1.12.1 release (or 1.13.0) with this fix? We hit this in production, and are downgrading to 1.11.0 as a consequence.

@Harinib-Kore
Copy link

I got the same problem . how to fix it

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

4 participants