some situations If you experience an error like: InconsistencyError: Probably the key ('_kombu.binding.celery') has been removed from the Redis database. then you may want to configure the redis-server - ** ---------- - *** --- * --- [Queues] -- ******* ---- . celery: exchange:celery(direct) binding:celery --- ***** ----- [2012-06-08 16:23:51,078: WARNING/MainProcess] celery@halcyon.local has message, **options) File "celery/backends/rpc.py", line 275, in on_task_call maybe_declare(self.binding(producer.channel), retry=True) File "/opt/celery/kombu/kombu/messaging.py", line 204, in _get_channel

some situations If you experience an error like: InconsistencyError: Probably the key ('_kombu.binding.celery') has been removed from the Redis database. then you may want to configure the redis-server - ** ---------- - *** --- * --- [Queues] -- ******* ---- . celery: exchange:celery(direct) binding:celery --- ***** ----- [2012-06-08 16:23:51,078: WARNING/MainProcess] celery@halcyon.local has message, **options) File "celery/backends/rpc.py", line 275, in on_task_call maybe_declare(self.binding(producer.channel), retry=True) File "/opt/celery/kombu/kombu/messaging.py", line 204, in _get_channel

some situations If you experience an error like: InconsistencyError: Probably the key ('_kombu.binding.celery') has been removed from the Redis database. then you may want to configure the redis-server - ** ---------- - *** --- * --- [Queues] -- ******* ---- . celery: exchange:celery(direct) binding:celery --- ***** ----- [2012-06-08 16:23:51,078: WARNING/MainProcess] celery@halcyon.local has message, **options) File "celery/backends/rpc.py", line 275, in on_task_call maybe_declare(self.binding(producer.channel), retry=True) File "/opt/celery/kombu/kombu/messaging.py", line 204, in _get_channel

AMQPs flexible routing model. Tasks can be routed to specific servers, or a cluster of servers by binding workers to different queues. A single worker node can be bound to one or more queues. Multiple messaging queues, video, image and lowpri that binds to the tasks exchange. For the queues we use the following binding keys: video: video.# image: image.# lowpri: misc.# Now we can send our tasks to different worker queue by using the following configuration: CELERY_QUEUES = {"default": {"exchange": "default", "binding_key": "default"}} CELERY_DEFAULT_QUEUE = "default" 2.8. Routing Tasks 51 Celery Documentation,

AMQPs flexible routing model. Tasks can be routed to specific servers, or a cluster of servers by binding workers to different queues. A single worker node can be bound to one or more queues. Multiple messaging queues, video, image and lowpri that binds to the tasks exchange. For the queues we use the following binding keys: video: video.# image: image.# lowpri: misc.# Now we can send our tasks to different worker queue by using the following configuration: CELERY_QUEUES = {"default": {"exchange": "default", "binding_key": "default"}} CELERY_DEFAULT_QUEUE = "default" How the queues are defined The point with this

queues, video, image and lowpri that bind to our tasks exchange. For the queues we use the following binding keys: video: video.# image: image.# lowpri: misc.# Now we can send our tasks to different worker Celery Documentation, Release 2.0.3 (stable) CELERY_QUEUES = {"default": {"exchange": "default", "binding_key": "default"}} CELERY_DEFAULT_QUEUE = "default" How the queues are defined The point with this configuration: CELERY_DEFAULT_QUEUE = "default" CELERY_QUEUES = { "default": { "binding_key": "task.#", }, "feed_tasks": { "binding_key": "feed.#", }, } CELERY_DEFAULT_EXCHANGE = "tasks" CELERY_DEFAULT_EXCHANGE_TYPE

queues, video, image and lowpri that bind to our tasks exchange. For the queues we use the following binding keys: video: video.# image: image.# lowpri: misc.# Now we can send our tasks to different worker "default": { "exchange": "default", "binding_key": "default"}, "videos": { "exchange": "media", "binding_key": "media.video", }, "images": { "exchange": "media", "binding_key": "media.image", } } CELERY_DEFAULT_QUEUE CELERY_DEFAULT_ROUTING_KEY = "default" NOTE: In Celery the routing_key is the key used to send the message, while binding_key is the key the queue is bound with. In the AMQP API they are both referred to as a routing key

AMQPs flexible routing model. Tasks can be routed to specific servers, or a cluster of servers by binding workers to different queues. A single worker node can be bound to one or more queues. Multiple messaging queues, video, image and lowpri that binds to the tasks exchange. For the queues we use the following binding keys: video: video.# image: image.# lowpri: misc.# Now we can send our tasks to different worker configuration: CELERY_QUEUES = {"default": {"exchange": "default", "binding_key": "default"}} CELERY_DEFAULT_QUEUE = "default" How the queues are defined The point with this

queues, video, image and lowpri that bind to our tasks exchange. For the queues we use the following binding keys: video: video.# image: image.# lowpri: misc.# Now we can send our tasks to different worker "default", "binding_key": "default"}, "videos": { "exchange": "media", "binding_key": "media.video", }, "images": { "exchange": "media", "binding_key": "media.image" CELERY_DEFAULT_ROUTING_KEY = "default" NOTE: In Celery the routing_key is the key used to send the message, while binding_key is the key the queue is bound with. In the AMQP API they are both referred to as a routing key

AMQPs flexible routing model. Tasks can be routed to specific servers, or a cluster of servers by binding workers to different queues. A single worker node can be bound to one or more queues. Multiple messaging queues, video, image and lowpri that binds to the tasks exchange. For the queues we use the following binding keys: video: video.# image: image.# lowpri: misc.# Now we can send our tasks to different worker configuration: CELERY_QUEUES = {"default": {"exchange": "default", "binding_key": "default"}} CELERY_DEFAULT_QUEUE = "default" How the queues are defined The point with this