selected result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Cassandra, or AMQP (message notification). Web- hooks Your tasks can 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. You have to ensure only a single last run times in a local database file (a shelve). django-celery also ships with a scheduler that stores the schedule in the Django database: $ celerybeat -S djcelery.schedulers.DatabaseScheduler Using

selected result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, Cassandra, or AMQP (message notification). Web- hooks 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. You have to ensure only a single last run times in a local database file (a shelve). django-celery also ships with a scheduler that stores the schedule in the Django database: $ celerybeat -S djcelery.schedulers.DatabaseScheduler Using

selected result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, Cassandra, or AMQP (message notification). Web- hooks 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. You have to ensure only a single last run times in a local database file (a shelve). django-celery also ships with a scheduler that stores the schedule in the Django database: 42 Chapter 2. User Guide Celery Documentation, Release 2.2

selected result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, AMQP (high performance). Web- hooks Your tasks can also 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. You have to ensure only a single last run times in a local database file (a shelve). django-celery also ships with a scheduler that stores the schedule in the Django database: 2.5. Periodic Tasks 41 Celery Documentation, Release 2.1.4

selected result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, Cassandra, or AMQP (message notification). Webhooks Your 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. You have to ensure only a single last run times in a local database file (a shelve). django-celery also ships with a scheduler that stores the schedule in the Django database: $ celerybeat -S djcelery.schedulers.DatabaseScheduler Using

selected result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Cassandra, or AMQP (message notification). Webhooks Your tasks can also 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. You have to ensure only a single python.org/dev/library/shelve.html#module-shelve]). django-celery also ships with a scheduler that stores the schedule in the Django database: $ celerybeat -S djcelery.schedulers.DatabaseScheduler Using

selected result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, AMQP (high performance). Webhooks Your tasks can also be 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. You have to ensure only a single last run times in a local database file (a shelve). django-celery also ships with a scheduler that stores the schedule in the Django database: $ celerybeat -S djcelery.schedulers.DatabaseScheduler Using

selected result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, Cassandra, or AMQP (message notification). Webhooks Your 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. You have to ensure only a single last run times in a local database file (a shelve). django-celery also ships with a scheduler that stores the schedule in the Django database: $ celerybeat -S djcelery.schedulers.DatabaseScheduler Using

2.2. Getting Started 7 Celery Documentation, Release 3.1.25 • threads/single threaded • Result Stores • AMQP, Redis • memcached, MongoDB • SQLAlchemy, Django ORM • Apache Cassandra • Serialization • some_task(self): if redis.ismember('tasks.revoked', self.request.id): raise Ignore() Example that stores results manually: from celery import states from celery.exceptions import Ignore @app.task(bind=True) 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. 108 Chapter 2. Contents Celery Documentation

and more… Concurrency prefork (multiprocessing), Eventlet, gevent threads/single threaded Result Stores AMQP, Redis memcached, MongoDB SQLAlchemy, Django ORM Apache Cassandra Serialization pickle, json some_task(self): if redis.ismember('tasks.revoked', self.request.id): raise Ignore() Example that stores results manually: from celery import states from celery.exceptions import Ignore @app.task(bind=True) 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. You have to ensure only a single