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

docs: moved Configuration to its own section

Browse Source 
* added more info on schedule catch up.
This commit is contained in:
Ilan
2015-08-19 12:38:15 +02:00
parent b99e16f108
commit 6610277b93
5 changed files with 201 additions and 184 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/cluster.rst
View File

@@ -42,14 +42,14 @@ Stopping the cluster with ctrl-c or either the ``SIGTERM`` and ``SIGKILL`` signa
16:44:14 [Q] INFO Process-1:9 stopped monitoring results
16:44:15 [Q] INFO Q Cluster-31781 has stopped.
The number of workers, optional timeouts, recycles and cpu_affinity can be controlled via the :ref:`configuration` settings.
The number of workers, optional timeouts, recycles and cpu_affinity can be controlled via the :doc:`configure` settings.
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 use the same cluster name. See :ref:`configuration`
- They use the same cluster name. See :doc:`configure`
- They share the same ``SECRET_KEY`` for Django.
Using a Procfile
@@ -80,7 +80,7 @@ An example :file:`circus.ini` ::
Note that we only start one process. It is not a good idea to run multiple instances of the cluster in the same environment since this does nothing to increase performance and in all likelihood will diminish it.
Control your cluster using the ``workers``, ``recycle`` and ``timeout`` settings in your :ref:`configuration`
Control your cluster using the ``workers``, ``recycle`` and ``timeout`` settings in your :doc:`configure`
Architecture
------------