testing_project/Documentation: reference/reference_lua/box_info/replication — English @ Weblate: :samp:`replication[{n}].upstream` appears (is not ``nil``) if the current instance is …

Source string Source string

English

:samp:`replication[{n}].upstream` appears (is not ``nil``) if the current instance is following or intending to follow instance *n*, which ordinarily means :samp:`replication[{n}].upstream.status` = ``follow``, :samp:`replication[{n}].upstream.peer` = url of instance *n* which is being followed, :samp:`replication[{n}].lag and idle` = the instance's speed, described later. Another way to say this is: :samp:`replication[{n}].upstream` will appear when :samp:`replication[{n}].upstream.peer` is not of the current instance, and is not read-only, and was specified in ``box.cfg{replication={...}}``, so it is shown in :ref:`box.cfg.replication <cfg_replication-replication>`.

Needs editing

Skip

	English	Actions
	box.info.replication
	The replication section of ``box.info()`` is a table with statistics for all instances in the replica set that the current instance belongs to. To see the example, refer to :ref:`Monitoring a replica set <replication-monitoring>`.
	In the following, n is the index number of one table item, for example, :samp:`replication[1]`, which has data about server instance number 1, which may or may not be the same as the current instance (the "current instance" is what is responding to ``box.info``).
	:samp:`replication[{n}].id` is a short numeric identifier of instance n within the replica set. This value is stored in the :ref:`box.space._cluster <box_space-cluster>` system space.
	:samp:`replication[{n}].uuid` is a globally unique identifier of instance n. This value is stored in the :ref:`box.space._cluster <box_space-cluster>` system space.
	:samp:`replication[{n}].lsn` is the :ref:`log sequence number <replication-mechanism>` (LSN) for the latest entry in instance n's :ref:`write-ahead log <index-box_persistence>` (WAL).
	:samp:`replication[{n}].upstream` appears (is not ``nil``) if the current instance is following or intending to follow instance n, which ordinarily means :samp:`replication[{n}].upstream.status` = ``follow``, :samp:`replication[{n}].upstream.peer` = url of instance n which is being followed, :samp:`replication[{n}].lag and idle` = the instance's speed, described later. Another way to say this is: :samp:`replication[{n}].upstream` will appear when :samp:`replication[{n}].upstream.peer` is not of the current instance, and is not read-only, and was specified in ``box.cfg{replication={...}}``, so it is shown in :ref:`box.cfg.replication <cfg_replication-replication>`.
	:samp:`replication[{n}].upstream.status` is the replication status of the connection with the instance n:
	``connect``: an instance is connecting to the master.
	``auth``: :ref:`authentication <authentication>` is being performed.
	``wait_snapshot``: an instance is receiving metadata from the master. If join fails with a non-critical :ref:`error <error_codes>` at this stage (for example, ``ER_READONLY``, ``ER_ACCESS_DENIED``, or a network-related issue), an instance tries to find a new master to join.
	``fetch_snapshot``: an instance is receiving data from the master's ``.snap`` files.
	``final_join``: an instance is receiving new data added during ``fetch_snapshot``.
	``sync``: the master and replica are synchronizing to have the same data.
	``follow``: the current instance's role is replica. This means that the instance is read-only or acts as a replica for this remote peer in :ref:`master-master <replication-roles>` configuration. The instance is receiving or able to receive data from the instance n's (upstream) master.
	``stopped``: replication is stopped due to a replication error (for example, :ref:`duplicate key <error_codes>`).
	``disconnected``: an instance is not connected to the replica set (for example, due to network issues, not replication errors).
	Learn more from :ref:`Replication stages <replication_stages>`.
	:samp:`replication[{n}].upstream.idle` is the time (in seconds) since the last event was received. This is the primary indicator of replication health. Learn more from :ref:`Monitoring a replica set <replication-monitoring>`.
	:samp:`replication[{n}].upstream.peer` contains instance n's :ref:`URI <index-uri>`, for example, 127.0.0.1:3302. Learn more from :ref:`Monitoring a replica set <replication-monitoring>`.
	:samp:`replication[{n}].upstream.lag` is the time difference between the local time of instance n, recorded when the event was received, and the local time at another master recorded when the event was written to the :ref:`write-ahead log <internals-wal>` on that master. Learn more from :ref:`Monitoring a replica set <replication-monitoring>`.
	:samp:`replication[{n}].upstream.message` contains an error message in case of a :ref:`degraded state <replication-recover>`; otherwise, it is ``nil``.

Loading…

None

New source string

testing_project / Documentation: reference/reference_lua/box_info/replication — English

:samp:`replication[{n}].upstream` appears (is not ``nil``) if the current instance is following or intending to follow instance *n*, which ordinarily means :samp:`replication[{n}].upstream.status` = ``follow``, :samp:`replication[{n}].upstream.peer` = url of instance *n* which is being followed, :samp:`replication[{n}].lag and idle` = the instance's speed, described later. Another way to say this is: :samp:`replication[{n}].upstream` will appear when :samp:`replication[{n}].upstream.peer` is not of the current instance, and is not read-only, and was specified in ``box.cfg{replication={...}}``, so it is shown in :ref:`box.cfg.replication <cfg_replication-replication>`.

a year ago

Browse all string changes

Things to check

Ellipsis

The string uses three dots (...) instead of an ellipsis character (…)

Reset

Glossary

English	English
No related strings found in the glossary.

String information

Flags

read-only

String age

a year ago

Last updated

a year ago

Source string age

a year ago

Translation file

string 7