fork/django-q2
1
0
Fork 0
mirror of https://github.com/django-q2/django-q2.git synced 2026-09-28 08:18:12 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: adjusted for multiple brokers

Browse Source
This commit is contained in:
Ilan Steemers
2015-09-06 14:48:33 +02:00
parent 44473ca408
commit 5e5bf2cc8d
6 changed files with 171 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/cluster.rst
+7 -5
View File
@@ -48,7 +48,7 @@ Multiple Clusters
-----------------
You can have multiple clusters on multiple machines, working on the same queue as long as:
- They connect to the same Redis server or Redis cluster.
- They connect to the same :doc:`broker<brokers>`.
- They use the same cluster name. See :doc:`configure`
- They share the same ``SECRET_KEY`` for Django.
@@ -92,15 +92,16 @@ Architecture
Signed Tasks
""""""""""""
Tasks are first pickled and then signed using Django's own :mod:`django.core.signing` module using the ``SECRET_KEY`` and cluster name as salt, before being sent to a Redis list. This ensures that task
packages on the Redis server can only be executed and read by clusters
Tasks are first pickled and then signed using Django's own :mod:`django.core.signing` module using the ``SECRET_KEY`` and cluster name as salt, before being sent to a message broker. This ensures that task
packages on the broker can only be executed and read by clusters
and django servers who share the same secret key and cluster name.
Optionally the packages can be compressed before transport
If a package fails to unpack, it will be marked failed with the broker and discarded.
Optionally the packages can be compressed before transport.
Pusher
""""""
The pusher process continuously checks the Redis list for new task
The pusher process continuously checks the broker for new task
packages. It checks the signing and unpacks the task to the Task Queue.
Worker
@@ -115,6 +116,7 @@ Monitor
The result monitor checks the Result Queue for processed packages and
saves both failed and successful packages to the Django database.
If the broker supports it, a delivery receipt is sent.
.. _sentinel: