status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #1970 from hashicorp/d-recommend-reap 

Recommend against adjusting reap times
This commit is contained in:
James Phillips 2016-04-21 14:56:23 -07:00
parent 6676e83656 0c7f697244
commit 763711686a
3 changed files with 15 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
website/source/docs/agent/basics.html.markdown
View File

@ -135,7 +135,9 @@ marks that node as having _left_. Unlike the _failed_ case, all of the
services provided by a node are immediately deregistered. If the agent was services provided by a node are immediately deregistered. If the agent was
a server, replication to it will stop. a server, replication to it will stop.
To prevent an accumulation of dead nodes (nodes in either _failed_ or _left_ states), To prevent an accumulation of dead nodes (nodes in either _failed_ or _left_
Consul will automatically remove dead nodes out of the catalog. This process is states), Consul will automatically remove dead nodes out of the catalog. This
called _reaping_. This is currently done on a configurable interval of 72 hours. process is called _reaping_. This is currently done on a configurable
Reaping is similar to leaving, causing all associated services to be deregistered. interval of 72 hours (changing the reap interval is *not* recommended due to
its consequences during outage situations). Reaping is similar to leaving,
causing all associated services to be deregistered.

2
website/source/docs/agent/options.html.markdown
View File

@ -516,7 +516,7 @@ Consul will not enable TLS for the HTTP API unless the `https` port has been ass
is implemented and enforced (i.e. DNS answers are always sorted and is implemented and enforced (i.e. DNS answers are always sorted and
therefore never random), clients may need to set this value to `1` to therefore never random), clients may need to set this value to `1` to
preserve the expected randomized distribution behavior (note: preserve the expected randomized distribution behavior (note:
[https://tools.ietf.org/html/rfc3484](RFC 3484) has been obsoleted by [RFC 3484](https://tools.ietf.org/html/rfc3484) has been obsoleted by
[RFC 6724](https://tools.ietf.org/html/rfc6724) and as a result it should [RFC 6724](https://tools.ietf.org/html/rfc6724) and as a result it should
be increasingly uncommon to need to change this value with modern be increasingly uncommon to need to change this value with modern
resolvers). resolvers).

12
website/source/docs/faq.html.markdown
View File

@ -59,10 +59,14 @@ the current state of the catalog can lag behind until the state is reconciled.
## Q: Are _failed_ or _left_ nodes ever removed? ## Q: Are _failed_ or _left_ nodes ever removed?
To prevent an accumulation of dead nodes (nodes in either _failed_ or _left_ states), To prevent an accumulation of dead nodes (nodes in either _failed_ or _left_
Consul will automatically remove dead nodes out of the catalog. This process is states), Consul will automatically remove dead nodes out of the catalog. This
called _reaping_. This is currently done on a configurable interval of 72 hours. process is called _reaping_. This is currently done on a configurable
Reaping is similar to leaving, causing all associated services to be deregistered. interval of 72 hours. Reaping is similar to leaving, causing all associated
services to be deregistered. Changing the reap interval for aesthetic
reasons to trim the number of _failed_ or _left_ nodes is not advised (nodes
in the _failed_ or _left_ state do not cause any additional burden on
Consul).
## Q: Does Consul support delta updates for watchers or blocking queries? ## Q: Does Consul support delta updates for watchers or blocking queries?