From 8ccc23beff28e42b7e4937c74f0b548a5203db93 Mon Sep 17 00:00:00 2001 From: Ryan Breen Date: Wed, 18 Mar 2015 12:56:12 -0400 Subject: [PATCH] Website: add node reaping detail to the FAQ. --- website/source/docs/faq.html.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/website/source/docs/faq.html.markdown b/website/source/docs/faq.html.markdown index f899783458..33f84777b4 100644 --- a/website/source/docs/faq.html.markdown +++ b/website/source/docs/faq.html.markdown @@ -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.