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: doc/book/replication/repl_monitoring.rst
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
Monitoring a replica set
4
4
========================
5
5
6
-
To learn what instances belong in the replica set, and obtain statistics for all
6
+
To learn what instances belong to the replica set and obtain statistics for all
7
7
these instances, issue a :doc:`/reference/reference_lua/box_info/replication` request:
8
8
9
9
.. code-block:: tarantoolsession
@@ -52,7 +52,7 @@ The primary indicators of replication health are:
52
52
53
53
.. _heartbeat:
54
54
55
-
* :ref:`idle <box_info_replication_upstream_idle>`, the time (in seconds) since
55
+
* :ref:`idle <box_info_replication_upstream_idle>`: the time (in seconds) since
56
56
the instance received the last event from a master.
57
57
58
58
If the master has no updates to send to the replicas, it sends heartbeat messages
@@ -65,7 +65,7 @@ The primary indicators of replication health are:
65
65
seriously behind, because the master is running ahead of the replica, or the
66
66
network link between the instances is down.
67
67
68
-
* :ref:`lag <box_info_replication_upstream_lag>`, the time difference between
68
+
* :ref:`lag <box_info_replication_upstream_lag>`: the time difference between
69
69
the local time at the instance, recorded when the event was received, and the
70
70
local time at another master recorded when the event was written to the
71
71
:ref:`write ahead log <internals-wal>` on that master.
@@ -75,3 +75,9 @@ The primary indicators of replication health are:
75
75
remote master clock being consistently behind the local instance's clock.
76
76
77
77
For multi-master configurations, ``lag`` is the maximal lag.
78
+
79
+
For better understanding, see the following diagram illustrating the ``upstream`` and ``downstream`` connections within the replica set of three instances:
The **replication** section of ``box.info()`` is a table array with
12
12
statistics for all instances in the replica set that the current instance
@@ -126,3 +126,10 @@ box.info.replication
126
126
``status = 'stopped'``, ``message = 'unexpected EOF when reading
127
127
from socket'``, and ``system_message = 'Broken pipe'``.
128
128
See also :ref:`degraded state <replication-recover>`.
129
+
130
+
131
+
For better understanding, see the following diagram illustrating the ``upstream`` and ``downstream`` connections within the replica set of three instances:
0 commit comments