Skip to content

Commit d45422c

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

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
@@ -49,7 +49,7 @@ A failed replication can either mean a real issue in the cluster (e.g., no leade
4949
It can be `APPLYING`, `REPLICATING`, or `UNAVAILABLE`.
5050
+
5151
** `APPLYING` means that the member can replicate and is actively applying transactions.
52-
`REPLICATING` means that the member can participate in replicating, but can't apply.
52+
** `REPLICATING` means that the member can participate in replicating, but can't apply.
5353
This state is uncommon, but may happen while waiting for the database to start and accept transactions.
5454
* *recognisedLeader:* shows the server id of the perceived leader of each primary member.
5555
* *recognisedLeaderTerm:* shows the term of the perceived leader of each primary member.

0 commit comments

Comments
 (0)