Menu
When I run syncdb, I notice a lot of tables created like:
django-kombu is providing the transport, so it can't be related to the actual queue. Even when I run tasks, I still see nothing populated in these tables. What are these tables used for? Monitoring purposes only -- if I enable it?
If so, is it also true that if I do a lookup of AsyncResult(), I'm guessing that is actually looking up the task result via the django-kombu tables instead of djcelery?
Thanks.
442
Celery makes it easier to implement the task queues for many workers in a Django application.
To use the Celery Beat, we need to configure the Redis server in the Django projects settings.py file. As we have installed the Redis server on the local machine, we will point the URL to localhost. The CELERY_TIMEZONE variable must be correctly set to run the tasks at the intended times.
Introduction. celery beat is a scheduler. It kicks off tasks at regular intervals, which are then executed by the worker nodes available in the cluster. By default the entries are taken from the CELERYBEAT_SCHEDULE setting, but custom stores can also be used, like storing the entries in an SQL database.
Yes you can. Celery is a generic asynchronous task queue. In place of "django_project" you would point to your module.
The celery task_state table, populated by the daemon celerycam, is just for monitoring purposes.
The other tables, like "crontabschedule" "intervals" etc. are for scheduling periodic tasks by using the django backend db. These tables are used when you launch celery in beat mode (-B) and when you have this var set in the settings
CELERYBEAT_SCHEDULER = "djcelery.schedulers.DatabaseScheduler"
In this way you tell celery to use the django db for schedule tasks.
116
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
