From 66a67ba5af93a06dd8bfd23406dd1ac36d3fa3ed Mon Sep 17 00:00:00 2001 From: Michael Johnson Date: Thu, 11 Jun 2020 09:08:53 -0700 Subject: [PATCH] Clarify health monitor behavior The basic cookbook document implied that pools without a health monitor would eventually remove a failed member from the pool. This will not happen as if there is not health monitor, the members are assumed as ONLINE. Change-Id: I6c52f163d8ac0456b4faf7d9bf5cc4a19ee6eeb7 --- doc/source/user/guides/basic-cookbook.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/source/user/guides/basic-cookbook.rst b/doc/source/user/guides/basic-cookbook.rst index 5c493d84ef..f5e9a39723 100644 --- a/doc/source/user/guides/basic-cookbook.rst +++ b/doc/source/user/guides/basic-cookbook.rst @@ -779,9 +779,9 @@ Health Monitor Best Practices ============================= While it is possible to set up a listener without a health monitor, if a back-end pool member goes down, Octavia will not remove the failed server from -the pool until a considerable time has passed. This can lead to service -disruption for web clients. Because of this, we recommend always configuring -production load balancers to use a health monitor. +the pool. This can lead to service disruption for web clients. Because of this, +we recommend always configuring production load balancers to use a health +monitor. The health monitor itself is a process that does periodic health checks on each back-end server to pre-emptively detect failed servers and temporarily pull