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
@@ -64,7 +64,7 @@ An example of an error is that one or more of the requested databases do not exi
64
64
* `TRUE` -- if this server managed to replicate the dummy transaction to a majority of cluster members within the given timeout.
65
65
* `FALSE` -- if it failed to replicate within the timeout.
66
66
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.
68
68
69
69
=== Possible values of `memberStatus`
70
70
* `APPLYING` means that the member can replicate and is actively applying transactions.
0 commit comments