Skip to content

Commit 671e6cf

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

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
@@ -44,7 +44,7 @@ The procedure returns a row for all primary members of all the requested databas
4444
** `TRUE` -- if this server managed to replicate the dummy transaction to a majority of cluster members within the given timeout.
4545
** `FALSE` -- if it failed to replicate within the timeout.
4646
The value is the same column-wise.
47-
A failed replication can either mean that there is a real issue in the cluster (e.g. no leader) or it may simply mean that this server is too far behind in apply, and can't therefore replicate.
47+
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.
4848
* *memberStatus:* shows the status of each primary member.
4949
It can either be `APPLYING`, `REPLICATING` or `UNAVAILABLE`.
5050
`APPLYING` means that the member can replicate and is actively applying transactions.

0 commit comments

Comments
 (0)