Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Upgrade Celery to 4.x
See original GitHub issueIssue Summary
Celery 3.x does not allow limiting worker memory usage. This means one worker can use all of host’s memory and affect function for other works and processes. Upgrading Celery to 4.x will allow adding --max-memory-per-child flag and limit the memory usage.
I understand that Mozilla is using Celery 4 with Redash, we’d like to hear about your experience and what it involved.
There is a discussion on Discourse at https://discuss.redash.io/t/upgrade-celery-to-4-x/1867 Please add your thoughts to that discussion.
@arikfr can you tag the Mozilla folks?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hey there, Mozilla engineer here, from what I’ve gathered from the ops folk, Celery 4 has beeen an improvement in terms of stability and responsiveness. But I’ll let @robotblake chime in with more details who is on the operations side of our Redash instance.
Redash v6 will use Celery v4.