diff options
| author |  Miek Gieben <miek@miek.nl>
| 2018-03-02 17:17:26 -0800 |
|---|---|---|
| committer |  GitHub <noreply@github.com>
| 2018-03-02 17:17:26 -0800 |
| commit | 6cec66ce404b8f680cca5d03584ebcbd1ab888e0 (patch) | |
| tree | d001f1c853dd52ad855db38a6cf4a7c382289917 /plugin/reload | |
| parent | 6f3a7af5486294c1ca5076e9c56827cd388900e7 (diff) | |
| download | coredns-6cec66ce404b8f680cca5d03584ebcbd1ab888e0.tar.gz coredns-6cec66ce404b8f680cca5d03584ebcbd1ab888e0.tar.zst coredns-6cec66ce404b8f680cca5d03584ebcbd1ab888e0.zip | |
plugin/reload: enable (#1587)
Couldn't revert the original commit, just manually perform the needed
tweaks.
Diffstat (limited to 'plugin/reload')
| -rw-r--r-- | plugin/reload/README.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/plugin/reload/README.md b/plugin/reload/README.md index bb4eda179..9ebbe2dda 100644 --- a/plugin/reload/README.md +++ b/plugin/reload/README.md @@ -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 |