Skip to content

Commit 7529c12

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

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
@@ -73,7 +73,7 @@ This state is uncommon, but may happen while waiting for the database to start a
7373
* `UNAVAILABLE` means that the member is either too far behind the leader or unreachable.
7474

7575
=== 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.
7777
* `FALSE` -- on the remaining servers.
7878

7979
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

Comments
 (0)