openstack
/
octavia
Code Issues Proposed changes

Merge "Clarify health monitor behavior"

This commit is contained in:
Zuul 2020-06-23 08:06:09 +00:00 committed by Gerrit Code Review
parent e92c72b970 66a67ba5af
commit e475734b2a
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
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