Tweaks wording in lifeguard section.

This commit is contained in:
James Phillips 2016-09-14 10:17:23 -07:00 committed by GitHub
parent c591d86dd5
commit f57b84b807

View File

@ -45,14 +45,14 @@ however as a developer to understand how this library is leveraged.
<a name="lifeguard"></a> <a name="lifeguard"></a>
## Lifeguard Enhancements ## Lifeguard Enhancements
Consul's Gossip Protocol, shared with HashiCorp's Serf, forms the basis of its powerful SWIM makes the assumption that the local node is healthy in the sense
distributed failure detector. Unfortunately, the algorithm on which it is based makes an that soft real-time processing of packets is possible. However, in cases
assumption that the local node is healthy in the sense that soft real-time processing of where the local node is experiencing CPU or network exhaustion this assumption
packets is possible. In Consul versions prior to 0.7, this can sometimes manifest in a can be violated. The result is that the `serfHealth` check status can
severely degraded node falsely accusing others of being failed, causing occasional flaps occassionally flap, resulting in false monitoring alarms, adding noise to
in the `serfHealth` check status for one or more healthy nodes. Consul 0.7 adds two Serf telemetry, and simply causing the overall cluster to waste CPU and network
Lifeguard enhancements to this algorithm to help performance in the presence of degraded resources diagnosing a failure that may not truly exist.
nodes.
Please see [Serf's gossip protocol guide](https://www.serf.io/docs/internals/gossip.html#lifeguard) Lifeguard completely resolves this issue with novel enhancements to SWIM.
for more details. Please see the [Serf's gossip protocol guide](https://www.serf.io/docs/internals/gossip.html#lifeguard)
section on Lifeguard for more details.