auth docs: fix one error and expand a bit on queues and threads

diff --git a/docs/performance.rst b/docs/performance.rst
index 82417d635873e40b86b90e31ab779c31f632d928..10a6bcddd5ecb60c78f9f87b999f6b2487d8dab6 100644 (file)
--- a/docs/performance.rst
+++ b/docs/performance.rst
@@ -62,6 +62,11 @@ To determine if PowerDNS is unable to keep up with packets, determine
 the value of the :ref:`stat-qsize-q` variable. This represents the number of
 packets waiting for database attention. During normal operations the
 queue should be small.
+This number is a total over all receiver threads.
+
+The :ref:`setting-max-queue-length` and :ref:`setting-overload-queue-length` settings determine how PowerDNS deals with growing queues.
+If the queue for a single receiver thread (and its associated distributor threads) grows beyond the ``overload`` number, queries are answered only from the packet cache so the database can hopefully recover.
+If we reach the ``max`` number, we consider the situation hopeless and respawn.
 
 The value of :ref:`setting-queue-limit` should be set to only keep queries in
 queue for as long as someone would be interested in knowing the answer. Many
@@ -260,7 +265,7 @@ Amount of packets in the packetcache
 
 qsize-q
 ^^^^^^^
-Number of packets waiting for database attention, only available if :ref:`setting-receiver-threads` > 1
+Number of packets waiting for database attention, only available if :ref:`setting-distributor-threads` > 1
 
 .. _stat-query-cache-hit:
 

diff --git a/docs/settings.rst b/docs/settings.rst
index 1c22a24375b4aa37ba31e221a7d43cf919a74eb7..f7c513930ebcee46c2d484c4e1fca677ce86cf9b 100644 (file)
--- a/docs/settings.rst
+++ b/docs/settings.rst
@@ -1228,6 +1228,7 @@ will generally suffice for most installations.
 
 If this many packets are waiting for database attention, consider the
 situation hopeless and respawn.
+This limit is per receiver thread.
 
 .. _setting-max-signature-cache-entries: