mirror of
https://gitlab.isc.org/isc-projects/bind9
synced 2025-08-30 14:07:59 +00:00
Merge branch '2850-the-list-of-fetches-at-the-end-of-rndc-recursing-output-is-very-poorly-explained-in-the-arm' into 'main'
Resolve "The list of fetches at the end of 'rndc recursing' output is very poorly explained in the ARM - what does 'allowed' mean?" Closes #2850 See merge request isc-projects/bind9!5388
This commit is contained in:
@@ -370,11 +370,24 @@ Currently supported commands are:
|
|||||||
avoids the need to examine the modification times of the zone files.
|
avoids the need to examine the modification times of the zone files.
|
||||||
|
|
||||||
``recursing``
|
``recursing``
|
||||||
This command dumps the list of queries ``named`` is currently recursing on, and the
|
This command dumps the list of queries ``named`` is currently
|
||||||
list of domains to which iterative queries are currently being sent.
|
recursing on, and the list of domains to which iterative queries
|
||||||
The second list includes the number of fetches currently active for
|
are currently being sent.
|
||||||
the given domain, and how many have been passed or dropped because of
|
|
||||||
the ``fetches-per-zone`` option.
|
The first list includes all unique clients that are waiting for
|
||||||
|
recursion to complete, including the query that is awaiting a
|
||||||
|
response and the timestamp (seconds since the Unix epoch) of
|
||||||
|
when named started processing this client query.
|
||||||
|
|
||||||
|
The second list comprises of domains for which there are active
|
||||||
|
(or recently active) fetches in progress. It reports the number
|
||||||
|
of active fetches for each domain and the number of queries that
|
||||||
|
have been passed (allowed) or dropped (spilled) as a result of
|
||||||
|
the ``fetches-per-zone`` limit. (Note: these counters are not
|
||||||
|
cumulative over time; whenever the number of active fetches for
|
||||||
|
a domain drops to zero, the counter for that domain is deleted,
|
||||||
|
and the next time a fetch is sent to that domain, it is recreated
|
||||||
|
with the counters set to zero).
|
||||||
|
|
||||||
``refresh`` *zone* [*class* [*view*]]
|
``refresh`` *zone* [*class* [*view*]]
|
||||||
This command schedules zone maintenance for the given zone.
|
This command schedules zone maintenance for the given zone.
|
||||||
|
@@ -2998,12 +2998,13 @@ system.
|
|||||||
|
|
||||||
The current list of active fetches can be dumped by running
|
The current list of active fetches can be dumped by running
|
||||||
``rndc recursing``. The list includes the number of active fetches
|
``rndc recursing``. The list includes the number of active fetches
|
||||||
for each domain and the number of queries that have been passed or
|
for each domain and the number of queries that have been passed
|
||||||
dropped as a result of the ``fetches-per-zone`` limit. (Note: these
|
(allowed) or dropped (spilled) as a result of the ``fetches-per-zone``
|
||||||
counters are not cumulative over time; whenever the number of active
|
limit. (Note: these counters are not cumulative over time;
|
||||||
fetches for a domain drops to zero, the counter for that domain is
|
whenever the number of active fetches for a domain drops to zero,
|
||||||
deleted, and the next time a fetch is sent to that domain, it is
|
the counter for that domain is deleted, and the next time a fetch
|
||||||
recreated with the counters set to zero.)
|
is sent to that domain, it is recreated with the counters set
|
||||||
|
to zero.)
|
||||||
|
|
||||||
``fetches-per-server``
|
``fetches-per-server``
|
||||||
This sets the maximum number of simultaneous iterative queries that the server
|
This sets the maximum number of simultaneous iterative queries that the server
|
||||||
|
@@ -372,11 +372,24 @@ full \fBreload\fP when there is a large number of zones, because it
|
|||||||
avoids the need to examine the modification times of the zone files.
|
avoids the need to examine the modification times of the zone files.
|
||||||
.TP
|
.TP
|
||||||
.B \fBrecursing\fP
|
.B \fBrecursing\fP
|
||||||
This command dumps the list of queries \fBnamed\fP is currently recursing on, and the
|
This command dumps the list of queries \fBnamed\fP is currently
|
||||||
list of domains to which iterative queries are currently being sent.
|
recursing on, and the list of domains to which iterative queries
|
||||||
The second list includes the number of fetches currently active for
|
are currently being sent.
|
||||||
the given domain, and how many have been passed or dropped because of
|
.sp
|
||||||
the \fBfetches\-per\-zone\fP option.
|
The first list includes all unique clients that are waiting for
|
||||||
|
recursion to complete, including the query that is awaiting a
|
||||||
|
response and the timestamp (seconds since the Unix epoch) of
|
||||||
|
when named started processing this client query.
|
||||||
|
.sp
|
||||||
|
The second list comprises of domains for which there are active
|
||||||
|
(or recently active) fetches in progress. It reports the number
|
||||||
|
of active fetches for each domain and the number of queries that
|
||||||
|
have been passed (allowed) or dropped (spilled) as a result of
|
||||||
|
the \fBfetches\-per\-zone\fP limit. (Note: these counters are not
|
||||||
|
cumulative over time; whenever the number of active fetches for
|
||||||
|
a domain drops to zero, the counter for that domain is deleted,
|
||||||
|
and the next time a fetch is sent to that domain, it is recreated
|
||||||
|
with the counters set to zero).
|
||||||
.TP
|
.TP
|
||||||
.B \fBrefresh\fP \fIzone\fP [\fIclass\fP [\fIview\fP]]
|
.B \fBrefresh\fP \fIzone\fP [\fIclass\fP [\fIview\fP]]
|
||||||
This command schedules zone maintenance for the given zone.
|
This command schedules zone maintenance for the given zone.
|
||||||
|
Reference in New Issue
Block a user