- Fix documentation for requestlist.overwritten and

  requestlist.exceeded, it explains which query was dropped.

diff --git a/doc/Changelog b/doc/Changelog
index 62e3089d1390ecf679ba334f0327708fe2e3f3d7..7563940a64d67e3be1e39b654b14870006f4cd6d 100644 (file)
--- a/doc/Changelog
+++ b/doc/Changelog
@@ -1,3 +1,7 @@
+15 January 2026: Wouter
+       - Fix documentation for requestlist.overwritten and
+         requestlist.exceeded, it explains which query was dropped.
+
 8 January 2026: Wouter
        - Merge #1381: Do not initialize quic_table unless it is enabled.
 

diff --git a/doc/unbound-control.rst b/doc/unbound-control.rst
index 630f2e160cd3badfa23366394a1a41705465bd86..2f5520824dd946a6176b93a9de770ee24defdcd7 100644 (file)
--- a/doc/unbound-control.rst
+++ b/doc/unbound-control.rst
@@ -897,12 +897,22 @@ number of statistic counters:
     entries.
     This happens if there is a flood of queries that recursive processing and
     the server has a hard time.
+    The counter is increased when during the flood the
+    :ref:`jostle-timeout<unbound.conf.jostle-timeout>`
+    allows a query to be removed in favor of a new incoming query.
+    The older query is then dropped to make space.
 
 
 @@UAHL@unbound-control.stats@threadX.requestlist.exceeded@@
     Queries that were dropped because the request list was full.
     This happens if a flood of queries need recursive processing, and the
     server can not keep up.
+    The counter is increased when during the flood there is no space
+    to be made with the jostle out of an older query, and the new query
+    is dropped.
+    Since no older queries are removed, see
+    :ref:`jostle-timeout<unbound.conf.jostle-timeout>` setting, there
+    is no space for the new query.
 
 
 @@UAHL@unbound-control.stats@threadX.requestlist.current.all@@