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
@@ -73,7 +73,7 @@ This state is uncommon, but may happen while waiting for the database to start a
73
73
* `UNAVAILABLE` means that the member is either too far behind the leader or unreachable.
74
74
75
75
=== Possible values of `requester`
76
-
* `TRUE` -- for the server on which the procedure is run
76
+
* `TRUE` -- for the server on which the procedure is run.
77
77
* `FALSE` -- on the remaining servers.
78
78
79
79
In general, you can use the `replicationSuccessful` field to determine overall write-availability, whereas the `memberStatus` field can be checked in order to see whether the database is fault-tolerant or not.
0 commit comments