docs: added queue_limit information

docs/install.rst

@@ -91,6 +91,16 @@ Limits the amount of successful tasks saved to Django.
  - Defaults to ``250``
  - Failures are always saved.
 
+.. _queue_limit:
+
+queue_limit
+~~~~~~~~~~~
+
+This does not limit the amount of tasks that can be queued overall on Redis, but rather how many tasks are kept in memory by a single cluster.
+Setting this to a reasonable number, can help balance the workload and the memory overhead of each individual cluster.
+It can also be used to manage the loss of data in case of a cluster failure.
+Defaults to ``None``, meaning no limit.
+
 label
 ~~~~~
 

docs/monitor.rst

@@ -46,6 +46,7 @@ TQ
 **Task Queue** counts the number of tasks in the queue
 
 If this keeps rising it means you are taking on more tasks than your cluster can handle.
+You can limit this by settings the :ref:`queue_limit` in your cluster configuration.
 
 RQ
 ~~
@@ -58,7 +59,7 @@ It's normal for the result queue to take slightly longer to clear than the task
 RC
 ~~
 
-**Reincarnations** shows the amount of processes that have been reincarnated after a sudden death or timeout.
+**Reincarnations** shows the amount of processes that have been reincarnated after a recycle, sudden death or timeout.
 If this number is unusually high, you are either suffering from repeated task errors or severe timeouts and you should check your logs for details.
 
 Up
@@ -124,9 +125,9 @@ Reference
 
     .. py:attribute:: pusher
 
-    The pid of the pushes process
+    The pid of the pusher process
 
-    .. py:attribute:: monitor
+    .. py:attribute:: monitormight
 
     The pid of the monitor process