Update image links (#24031)
This commit is contained in:
parent
3e74ca739e
commit
836f9612b8
16 changed files with 51 additions and 51 deletions
|
|
@ -557,7 +557,7 @@ order to account for network issues that sometimes occur on such platforms.
|
|||
The following chart illustrates how *phi* increase with increasing time since the
|
||||
previous heartbeat.
|
||||
|
||||

|
||||

|
||||
|
||||
Phi is calculated from the mean and standard deviation of historical
|
||||
inter arrival times. The previous chart is an example for standard deviation
|
||||
|
|
@ -565,7 +565,7 @@ of 200 ms. If the heartbeats arrive with less deviation the curve becomes steepe
|
|||
i.e. it is possible to determine failure more quickly. The curve looks like this for
|
||||
a standard deviation of 100 ms.
|
||||
|
||||

|
||||

|
||||
|
||||
To be able to survive sudden abnormalities, such as garbage collection pauses and
|
||||
transient network failures the failure detector is configured with a margin,
|
||||
|
|
@ -574,7 +574,7 @@ adjust the [configuration](#cluster-configuration) of this depending on your env
|
|||
This is how the curve looks like for `acceptable-heartbeat-pause` configured to
|
||||
3 seconds.
|
||||
|
||||

|
||||

|
||||
|
||||
Death watch uses the cluster failure detector for nodes in the cluster, i.e. it detects
|
||||
network failures and JVM crashes, in addition to graceful termination of watched
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue