Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-10-27 08:14:18 -04:00
Code Issues Packages Projects Releases Wiki Activity

plugin/reload: enable (#1587)

Browse Source 
Couldn't revert the original commit, just manually perform the needed
tweaks.
This commit is contained in:
Miek Gieben
2018-03-02 17:17:26 -08:00
committed by GitHub
parent 6f3a7af548
commit 6cec66ce40
4 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
plugin/reload/README.md
View File

@@ -15,7 +15,7 @@ The reloads are graceful - you should not see any loss of service when the
reload happens. Even if the new Corefile has an error, CoreDNS will continue
to run the old config and an error message will be printed to the log.
In some environments (for example, Kubernetes), there may be many CoreDNS
In some environments (for example, Kubernetes), there may be many CoreDNS
instances that started very near the same time and all share a common
Corefile. To prevent these all from reloading at the same time, some
jitter is added to the reload check interval. This is jitter from the
@@ -44,7 +44,7 @@ reload [INTERVAL] [JITTER]
Check with the default intervals:
~~~ txt
~~~ corefile
. {
reload
erratic
@@ -53,7 +53,7 @@ Check with the default intervals:
Check every 10 seconds (jitter is automatically set to 10 / 2 = 5 in this case):
~~~ txt
~~~ corefile
. {
reload 10s
erratic