Website: add node reaping detail to the FAQ.

This commit is contained in:
Ryan Breen 2015-03-18 12:56:12 -04:00
parent ff6e8852ce
commit aaf0ef78f4
1 changed files with 6 additions and 0 deletions

View File

@ -67,3 +67,9 @@ interact with the service catalog and are strongly consistent. Updates to the
catalog may come via the gossip protocol which is eventually consistent, meaning
the current state of the catalog can lag behind until the state is reconciled.
## Q: Are failed nodes ever removed?
To prevent an accumulation of dead nodes, Consul will automatically reap failed
nodes out of the catalog as well. This is currently done on a non-configurable
interval of 72 hours. Reaping is similar to leaving, causing all associated
services to be deregistered.