You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/clustering/monitoring/status-check.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ The procedure returns a row for all primary members of all the requested databas
44
44
** `TRUE` -- if this server managed to replicate the dummy transaction to a majority of cluster members within the given timeout.
45
45
** `FALSE` -- if it failed to replicate within the timeout.
46
46
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.
48
48
* *memberStatus:* shows the status of each primary member.
49
49
It can either be `APPLYING`, `REPLICATING` or `UNAVAILABLE`.
50
50
`APPLYING` means that the member can replicate and is actively applying transactions.
0 commit comments