=================================

celery - Distributed Task Queue

.. image:: http://cloud.github.com/downloads/ask/celery/celery_favicon_128.png

:Version: 2.2.1 :Web: http://celeryproject.org/ :Download: http://pypi.python.org/pypi/celery/ :Source: http://github.com/ask/celery/ :Keywords: task queue, job queue, asynchronous, rabbitmq, amqp, redis, python, webhooks, queue, distributed

–

.. _celery-synopsis:

Celery is an open source asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.

The execution units, called tasks, are executed concurrently on one or more worker nodes using multiprocessing, Eventlet_ or gevent_. Tasks can execute asynchronously (in the background) or synchronously (wait until ready).

Celery is used in production systems to process millions of tasks a day.

Celery is written in Python, but the protocol can be implemented in any language. It can also operate with other languages using webhooks_.

The recommended message broker is RabbitMQ, but limited support for Redis, Beanstalk, MongoDB, CouchDB_ and databases (using SQLAlchemy_ or the Django ORM_) is also available.

Celery is easy to integrate with Django, Pylons and Flask, using the django-celery, celery-pylons_ and Flask-Celery_ add-on packages.

.. _RabbitMQ: http://www.rabbitmq.com/ .. _Redis: http://code.google.com/p/redis/ .. _SQLAlchemy: http://www.sqlalchemy.org/ .. _Django: http://djangoproject.com/ .. _Django ORM: http://djangoproject.com/ .. _Eventlet: http://eventlet.net/ .. _gevent: http://gevent.org/ .. _Beanstalk: http://kr.github.com/beanstalkd/ .. _MongoDB: http://mongodb.org/ .. _CouchDB: http://couchdb.apache.org/ .. _Pylons: http://pylonshq.com/ .. _Flask: http://flask.pocoo.org/ .. _django-celery: http://pypi.python.org/pypi/django-celery .. _celery-pylons: http://pypi.python.org/pypi/celery-pylons .. _Flask-Celery: http://github.com/ask/flask-celery/ .. _operate with other languages using webhooks: http://ask.github.com/celery/userguide/remote-tasks.html

.. contents:: :local:

.. _celery-overview:

Overview

This is a high level overview of the architecture.

.. image:: http://cloud.github.com/downloads/ask/celery/Celery-Overview-v4.jpg

The broker delivers tasks to the worker nodes. A worker node is a networked machine running celeryd. This can be one or more machines depending on the workload.

The result of the task can be stored for later retrieval (called its “tombstone”).

.. _celery-example:

Example

You probably want to see some code by now, so here’s an example task adding two numbers: ::

from celery.task import task

@task
def add(x, y):
    return x + y

You can execute the task in the background, or wait for it to finish::

>>> result = add.delay(4, 4)
>>> result.wait() # wait for and return the result
8

Simple!

.. _celery-features:

Features

+-----------------+----------------------------------------------------+
| Messaging       | Supported brokers include `RabbitMQ`_, `Redis`_,   |
|                 | `Beanstalk`_, `MongoDB`_, `CouchDB`_, and popular  |
|                 | SQL databases.                                     |
+-----------------+----------------------------------------------------+
| Fault-tolerant  | Excellent configurable error recovery when using   |
|                 | `RabbitMQ`, ensures your tasks are never lost.     |
|                 | scenarios, and your tasks will never be lost.      |
+-----------------+----------------------------------------------------+
| Distributed     | Runs on one or more machines. Supports             |
|                 | broker `clustering`_ and `HA`_ when used in        |
|                 | combination with `RabbitMQ`_.  You can set up new  |
|                 | workers without central configuration (e.g. use    |
|                 | your grandma's laptop to help if the queue is      |
|                 | temporarily congested).                            |
+-----------------+----------------------------------------------------+
| Concurrency     | Concurrency is achieved by using multiprocessing,  |
|                 | `Eventlet`_, `gevent` or a mix of these.           |
+-----------------+----------------------------------------------------+
| Scheduling      | Supports recurring tasks like cron, or specifying  |
|                 | an exact date or countdown for when after the task |
|                 | should be executed.                                |
+-----------------+----------------------------------------------------+
| Latency         | Low latency means you are able to execute tasks    |
|                 | *while the user is waiting*.                       |
+-----------------+----------------------------------------------------+
| Return Values   | Task return values can be saved to the 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 tasks can also be HTTP callbacks, enabling    |
|                 | cross-language communication.                      |
+-----------------+----------------------------------------------------+
| Rate limiting   | Supports rate limiting by using the token bucket   |
|                 | algorithm, which accounts for bursts of traffic.   |
|                 | Rate limits can be set for each task type, or      |
|                 | globally for all.                                  |
+-----------------+----------------------------------------------------+
| Routing         | Using AMQP's flexible routing model you can route  |
|                 | tasks to different workers, or select different    |
|                 | message topologies, by configuration or even at    |
|                 | runtime.                                           |
+-----------------+----------------------------------------------------+
| Remote-control  | Worker nodes can be controlled from remote by      |
|                 | using broadcast messaging.  A range of built-in    |
|                 | commands exist in addition to the ability to       |
|                 | easily define your own. (AMQP/Redis only)          |
+-----------------+----------------------------------------------------+
| Monitoring      | You can capture everything happening with the      |
|                 | workers in real-time by subscribing to events.     |
|                 | A real-time web monitor is in development.         |
+-----------------+----------------------------------------------------+
| Serialization   | Supports Pickle, JSON, YAML, or easily defined     |
|                 | custom schemes. One task invocation can have a     |
|                 | different scheme than another.                     |
+-----------------+----------------------------------------------------+
| Tracebacks      | Errors and tracebacks are stored and can be        |
|                 | investigated after the fact.                       |
+-----------------+----------------------------------------------------+
| UUID            | Every task has an UUID (Universally Unique         |
|                 | Identifier), which is the task id used to query    |
|                 | task status and return value.                      |
+-----------------+----------------------------------------------------+
| Retries         | Tasks can be retried if they fail, with            |
|                 | configurable maximum number of retries, and delays |
|                 | between each retry.                                |
+-----------------+----------------------------------------------------+
| Task Sets       | A Task set is a task consisting of several         |
|                 | sub-tasks. You can find out how many, or if all    |
|                 | of the sub-tasks has been executed, and even       |
|                 | retrieve the results in order. Progress bars,      |
|                 | anyone?                                            |
+-----------------+----------------------------------------------------+
| Made for Web    | You can query status and results via URLs,         |
|                 | enabling the ability to poll task status using     |
|                 | Ajax.                                              |
+-----------------+----------------------------------------------------+
| Error E-mails   | Can be configured to send e-mails to the           |
|                 | administrators when tasks fails.                   |
+-----------------+----------------------------------------------------+

.. _clustering: http://www.rabbitmq.com/clustering.html .. _HA: http://www.rabbitmq.com/pacemaker.html .. _AMQP: http://www.amqp.org/ .. _Stomp: http://stomp.codehaus.org/ .. _Tokyo Tyrant: http://tokyocabinet.sourceforge.net/

.. _celery-documentation:

Documentation

The latest documentation_ with user guides, tutorials and API reference is hosted at Github.

.. _latest documentation: http://ask.github.com/celery/

.. _celery-installation:

Installation

You can install Celery either via the Python Package Index (PyPI) or from source.

To install using pip,::

$ pip install Celery

To install using easy_install,::

$ easy_install Celery

.. _celery-installing-from-source:

Downloading and installing from source

Download the latest version of Celery from http://pypi.python.org/pypi/celery/

You can install it by doing the following,::

$ tar xvfz celery-0.0.0.tar.gz
$ cd celery-0.0.0
$ python setup.py build
# python setup.py install # as root

.. _celery-installing-from-git:

Using the development version

You can clone the repository by doing the following::

$ git clone git://github.com/ask/celery.git

.. _getting-help:

Getting Help

.. _mailing-list:

Mailing list

For discussions about the usage, development, and future of celery, please join the celery-users_ mailing list.

.. _celery-users: http://groups.google.com/group/celery-users/

.. _irc-channel:

IRC

Come chat with us on IRC. The #celery_ channel is located at the Freenode_ network.

.. _#celery: irc://irc.freenode.net/celery .. _Freenode: http://freenode.net

.. _bug-tracker:

Bug tracker

If you have any suggestions, bug reports or annoyances please report them to our issue tracker at http://github.com/ask/celery/issues/

.. _wiki:

Wiki

http://wiki.github.com/ask/celery/

.. _contributing-short:

Contributing

Development of celery happens at Github: http://github.com/ask/celery

You are highly encouraged to participate in the development of celery. If you don’t like Github (for some reason) you’re welcome to send regular patches.

Be sure to also read the Contributing to Celery_ section in the documentation.

.. _Contributing to Celery: http://ask.github.com/celery/contributing.html

.. _license:

License

This software is licensed under the New BSD License. See the LICENSE file in the top distribution directory for the full license text.

.. # vim: syntax=rst expandtab tabstop=4 shiftwidth=4 shiftround