Build your Celery (the distributed task queue, not the vegetable) skills
with weekly tutorials,
how-tos and articles about common gotchas.
Estimated reading time: 4 minutes
Posted by Bjoern Stiel
I previously wrote about how to customise your Celery log handlers. But there is another Celery logger, the celery.task logger. The celery.task logger is a special logger set up by the Celery worker. Its goal is to add task-related information to the log messages. It exposes two new parameters:
Estimated reading time: 8 minutes
Posted by Bjoern Stiel
Have you ever asked yourself what happens when you start a Celery worker? Ok, it might not have been on your mind. But you might have come across things like execution pool, concurrency settings, prefork, gevent, eventlet and solo. So, what is it all about? How does it all fit together? And how is it related to the mechanics of...
Estimated reading time: 5 minutes
Posted by Bjoern Stiel
A flower, sometimes known as bloom or blossom, is the reproductive structure found in flowering plants. Celery is a marshland plant in the family in the family Apicaeae that has been cultivated as a vegetable since antiquity. A docker is a waterfront manual laborer who is involved in loading and unloading ships, trucks, trains or airplanes – Wikipedia.
Estimated reading time: 4 minutes
Posted by Bjoern Stiel
Have you ever dockerized your Celery app and wondered where the Celery worker bannker in the docker log output went? Usually, when you start your Celery worker, it comes up with a startup screen that displays useful information like version, broker, result backend, concurrency and subscribed queues.
Estimated reading time: 6 minutes
Posted by Bjoern Stiel
Celery tasks always have a state. If a task finished executing successfully, its state is SUCCESS. If a task execution resulted in an exception, its state is FAILURE. Celery knows six built-in states: