From: Florian Forster Date: Tue, 29 Nov 2016 07:56:42 +0000 (+0100) Subject: collectd.conf(5): s/TSDN/TSDB/ X-Git-Tag: collectd-5.8.0~262^2~2 X-Git-Url: https://git.verplant.org/?a=commitdiff_plain;h=d903c891496de59ae432df3a5bf085c09c883021;p=collectd.git collectd.conf(5): s/TSDN/TSDB/ --- diff --git a/src/collectd.conf.pod b/src/collectd.conf.pod index b043a89f..489b7e0b 100644 --- a/src/collectd.conf.pod +++ b/src/collectd.conf.pod @@ -8163,11 +8163,11 @@ Global directives are: =item B I -When I connects to a TSDB node, it will request the DNS. This can -become a problem if the TSDN node is unavailable or badly configured because -collectd will request DNS in order to reconnect for every metric, which can -flood your DNS. So you can cache the last value for I seconds -(default: B<600>, i.e. 10 minutes). +When I connects to a TSDB node, it will request the hostname from +DNS. This can become a problem if the TSDB node is unavailable or badly +configured because collectd will request DNS in order to reconnect for every +metric, which can flood your DNS. So you can cache the last value for +I seconds (default: B<600>, i.e. 10 minutes). You can also define a jitter, a random interval to wait in addition to I. This prevents all your collectd servers to resolve the