openstack
/
octavia
Code Issues Proposed changes

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
This commit is contained in:
Michael Johnson 2020-06-11 09:08:53 -07:00
parent aee9cd6fe4
commit 66a67ba5af
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/source/user/guides/basic-cookbook.rst
View File

@ -779,9 +779,9 @@ Health Monitor Best Practices
============================= =============================
While it is possible to set up a listener without a health monitor, if a 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 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 the pool. This can lead to service disruption for web clients. Because of this,
disruption for web clients. Because of this, we recommend always configuring we recommend always configuring production load balancers to use a health
production load balancers to use a health monitor. monitor.
The health monitor itself is a process that does periodic health checks on each 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 back-end server to pre-emptively detect failed servers and temporarily pull