Update cluster.md

Fixed a simple typo

(cherry picked from commit d357edccd1b2f0ecdb2445396da9a571fe883a50)
This commit is contained in:
Jabir S. Minjibir 2020-10-18 12:04:19 +01:00 committed by Patrik Nordwall
parent 568833543c
commit c71b40d05f

View file

@ -270,7 +270,7 @@ be necessary to set the nodes status to `Down` in order to complete the remov
In many cases a member can gracefully exit from the cluster, as described in @ref:[Leaving](#leaving), but In many cases a member can gracefully exit from the cluster, as described in @ref:[Leaving](#leaving), but
there are scenarios when an explicit downing decision is needed before it can be removed. For example in case there are scenarios when an explicit downing decision is needed before it can be removed. For example in case
of abrupt termination of the the JVM process, system overload that doesn't recover, or network partitions of abrupt termination of the the JVM process, system overload that doesn't recover, or network partitions
that don't heal. I such cases the node(s) will be detected as unreachable by other nodes, but they must also that don't heal. In such cases, the node(s) will be detected as unreachable by other nodes, but they must also
be marked as `Down` before they are removed. be marked as `Down` before they are removed.
When a member is considered by the failure detector to be `unreachable` the When a member is considered by the failure detector to be `unreachable` the