Skip to content

Commit a327a52

Browse files
Update modules/ROOT/pages/clustering/monitoring/status-check.adoc
Co-authored-by: NataliaIvakina <[email protected]>
1 parent 1355efb commit a327a52

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

modules/ROOT/pages/clustering/monitoring/status-check.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ An example of an error is that one or more of the requested databases do not exi
6464
* `TRUE` -- if this server managed to replicate the dummy transaction to a majority of cluster members within the given timeout.
6565
* `FALSE` -- if it failed to replicate within the timeout.
6666
The value is the same column-wise.
67-
A failed replication can either mean a real issue in the cluster (e.g., no leader) or that this server is too far behind in apply and can't replicate.
67+
A failed replication can either indicate a real issue in the cluster (e.g., no leader) or that this server is too far behind in applying updates and can't replicate.
6868

6969
=== Possible values of `memberStatus`
7070
* `APPLYING` means that the member can replicate and is actively applying transactions.

0 commit comments

Comments
 (0)