MINOR: dns: default "hold obsolete" timeout set to 0
The "hold obsolete" timer is used to prevent HAProxy from moving a server to
an other IP or from considering the server as DOWN if the IP currently
affected to this server has not been seen for this period of time in DNS
responses.
That said, historically, HAProxy used to update servers as soon as the IP
has disappeared from the response. Current default timeout break this
historical behavior and may change HAProxy's behavior when people will
upgrade to 1.8.
This patch changes the default value to 0 to keep backward compatibility.
diff --git a/doc/configuration.txt b/doc/configuration.txt
index 8aafbe3..66c9325 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -11734,7 +11734,7 @@
answer was in <status>. It follows the HAProxy time format.
<period> is in milliseconds by default.
- Default value is 10s for "valid" and 30s for others.
+ Default value is 10s for "valid", 0s for "obsolete" and 30s for others.
Note: since the name resolution is triggered by the health checks, a new
resolution is triggered after <period> modulo the <inter> parameter of