Add documentation for stale-answer-client-timeout
This commit is contained in:
@@ -403,6 +403,7 @@ OPTIONS
|
||||
sig-validity-interval integer [ integer ];
|
||||
sortlist { address_match_element; ... };
|
||||
stacksize ( default | unlimited | sizeval );
|
||||
stale-answer-client-timeout ( disabled | off | integer );
|
||||
stale-answer-enable boolean;
|
||||
stale-answer-ttl duration;
|
||||
stale-cache-enable boolean;
|
||||
@@ -806,6 +807,7 @@ VIEW
|
||||
sig-signing-type integer;
|
||||
sig-validity-interval integer [ integer ];
|
||||
sortlist { address_match_element; ... };
|
||||
stale-answer-client-timeout ( disabled | off | integer );
|
||||
stale-answer-enable boolean;
|
||||
stale-answer-ttl duration;
|
||||
stale-cache-enable boolean;
|
||||
|
||||
@@ -1832,6 +1832,20 @@ Boolean Options
|
||||
Information about stale answers is logged under the ``serve-stale``
|
||||
log category.
|
||||
|
||||
``stale-answer-client-timeout``
|
||||
This option defines the amount of time ``named`` waits before attempting to
|
||||
answer the query with a stale RRset from cache. If a stale answer is found,
|
||||
``named`` continues the ongoing fetches, attempting to refresh the RRset in
|
||||
cache until the ``resolver-query-timeout`` interval is reached.
|
||||
|
||||
The default value is ``1800`` (in milliseconds) and the maximum value is
|
||||
bounded to ``resolver-query-timeout`` minus one second. A value of ``0``
|
||||
immediately returns a cached RRset if available, and still attempts a refresh
|
||||
of the data in cache.
|
||||
|
||||
The option can be disabled by setting the value to ``off`` or ``disabled``.
|
||||
It also has no effect if ``stale-answer-enable`` is disabled.
|
||||
|
||||
``stale-cache-enable``
|
||||
If ``yes``, enable the retaining of "stale" cached answers. Default ``no``.
|
||||
|
||||
|
||||
@@ -466,6 +466,7 @@ options {
|
||||
sig\-validity\-interval integer [ integer ];
|
||||
sortlist { address_match_element; ... };
|
||||
stacksize ( default | unlimited | sizeval );
|
||||
stale\-answer\-client\-timeout ( disabled | off | integer );
|
||||
stale\-answer\-enable boolean;
|
||||
stale\-answer\-ttl duration;
|
||||
stale\-cache\-enable boolean;
|
||||
@@ -901,6 +902,7 @@ view string [ class ] {
|
||||
sig\-signing\-type integer;
|
||||
sig\-validity\-interval integer [ integer ];
|
||||
sortlist { address_match_element; ... };
|
||||
stale\-answer\-client\-timeout ( disabled | off | integer );
|
||||
stale\-answer\-enable boolean;
|
||||
stale\-answer\-ttl duration;
|
||||
stale\-cache\-enable boolean;
|
||||
|
||||
@@ -333,6 +333,7 @@ options {
|
||||
sig-validity-interval <integer> [ <integer> ];
|
||||
sortlist { <address_match_element>; ... };
|
||||
stacksize ( default | unlimited | <sizeval> );
|
||||
stale-answer-client-timeout ( disabled | off | <integer> );
|
||||
stale-answer-enable <boolean>;
|
||||
stale-answer-ttl <duration>;
|
||||
stale-cache-enable <boolean>;
|
||||
@@ -696,6 +697,7 @@ view <string> [ <class> ] {
|
||||
sig-signing-type <integer>;
|
||||
sig-validity-interval <integer> [ <integer> ];
|
||||
sortlist { <address_match_element>; ... };
|
||||
stale-answer-client-timeout ( disabled | off | <integer> );
|
||||
stale-answer-enable <boolean>;
|
||||
stale-answer-ttl <duration>;
|
||||
stale-cache-enable <boolean>;
|
||||
|
||||
@@ -331,6 +331,7 @@ options {
|
||||
sig-validity-interval <integer> [ <integer> ];
|
||||
sortlist { <address_match_element>; ... };
|
||||
stacksize ( default | unlimited | <sizeval> );
|
||||
stale-answer-client-timeout ( disabled | off | <integer> );
|
||||
stale-answer-enable <boolean>;
|
||||
stale-answer-ttl <duration>;
|
||||
stale-cache-enable <boolean>;
|
||||
@@ -692,6 +693,7 @@ view <string> [ <class> ] {
|
||||
sig-signing-type <integer>;
|
||||
sig-validity-interval <integer> [ <integer> ];
|
||||
sortlist { <address_match_element>; ... };
|
||||
stale-answer-client-timeout ( disabled | off | <integer> );
|
||||
stale-answer-enable <boolean>;
|
||||
stale-answer-ttl <duration>;
|
||||
stale-cache-enable <boolean>;
|
||||
|
||||
@@ -259,6 +259,7 @@
|
||||
sig-validity-interval <integer> [ <integer> ];
|
||||
sortlist { <address_match_element>; ... };
|
||||
stacksize ( default | unlimited | <sizeval> );
|
||||
stale-answer-client-timeout ( disabled | off | <integer> );
|
||||
stale-answer-enable <boolean>;
|
||||
stale-answer-ttl <duration>;
|
||||
stale-cache-enable <boolean>;
|
||||
|
||||
@@ -26,6 +26,23 @@ New Features
|
||||
|
||||
- None.
|
||||
|
||||
- A new option, ```stale-answer-client-timeout``, has been added to
|
||||
improve ``named``'s behavior with respect to serving stale data. The option
|
||||
defines the amount of time ``named`` waits before attempting
|
||||
to answer the query with a stale RRset from cache. If a stale answer
|
||||
is found, ``named`` continues the ongoing fetches, attempting to
|
||||
refresh the RRset in cache until the ``resolver-query-timeout`` interval is
|
||||
reached.
|
||||
|
||||
The default value is ``1800`` (in milliseconds) and the maximum value is
|
||||
bounded to ``resolver-query-timeout`` minus one second. A value of
|
||||
``0`` immediately returns a cached RRset if available, and still
|
||||
attempts a refresh of the data in cache.
|
||||
|
||||
The option can be disabled by setting the value to ``off`` or
|
||||
``disabled``. It also has no effect if ``stale-answer-enable`` is
|
||||
disabled.
|
||||
|
||||
Removed Features
|
||||
~~~~~~~~~~~~~~~~
|
||||
|
||||
|
||||
Reference in New Issue
Block a user