Overview

Project website www.tarantool.io/en/doc/latest
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@github.com:tarantool/doc.git
Repository branch test-weblate
Weblate repository http://weblate.tarantool.io/git/testing_project/documentation-bookadminreplicationrepl_reseed/
File mask locale/*/LC_MESSAGES/book/admin/replication/repl_monitoring.po
Translation file Download locale/ru/LC_MESSAGES/book/admin/replication/repl_monitoring.po
Last change None
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 13 328 2,559
Translated 61% 8 58% 192 59% 1,524
Needs editing 30% 4 35% 116 34% 880
Read-only 0% 0 0% 0 0% 0
Failing checks 7% 1 15% 52 25% 640
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 7% 1 6% 20 6% 155
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 15 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb

Quick numbers

328
Hosted words
13
Hosted strings
61%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+61%
—
Contributors
—
User avatar None

New strings to translate

testing_project / Documentation: book/admin/replication/repl_monitoring — Russian

5 new strings to translate appeared to the translation. a year ago
User avatar None

Resource update

testing_project / Documentation: book/admin/replication/repl_monitoring — Russian

File locale/ru/LC_MESSAGES/book/admin/replication/repl_monitoring.po was added. a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/replication/repl_monitoring — Russian

For better understanding, see the following diagram illustrating the ``upstream`` and ``downstream`` connections within the replica set of three instances:
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/replication/repl_monitoring — Russian

For multi-master configurations, ``lag`` is the maximal lag.
Для многомастерной конфигурации это максимально возможное отставание.
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/replication/repl_monitoring — Russian

Since the ``lag`` calculation uses the operating system clocks from two different machines, do not be surprised if it’s negative: a time drift may lead to the remote master clock being consistently behind the local instance's clock.
Поскольку при расчете ``отставания`` используются часы операционной системы с двух разных машин, не удивляйтесь, получив отрицательное число: смещение во времени может привести к постоянному запаздыванию времени на удаленном мастере относительно часов на локальном экземпляре.
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/replication/repl_monitoring — Russian

:ref:`lag <box_info_replication_upstream_lag>`: the time difference between the local time at the instance, 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.
:ref:`отставание <box_info_replication_upstream_lag>`, разница во времени между локальным временем на экземпляре, зарегистрированным при получении события, и локальное время на другом мастере, зарегистрированное при записи события в :ref:`журнал упреждающей записи <internals-wal>` на этом мастере.
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/replication/repl_monitoring — Russian

Therefore, in a healthy replication setup, ``idle`` should never exceed ``replication_timeout``: if it does, either the replication is lagging seriously behind, because the master is running ahead of the replica, or the network link between the instances is down.
Таким образом, в работоспособном состоянии значение ``idle`` никогда не должно превышать значение ``replication_timeout``: в противном случае, либо репликация сильно отстает, поскольку мастер опережает реплику, либо отсутствует сетевое подключение между экземплярами.
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/replication/repl_monitoring — Russian

If the master has no updates to send to the replicas, it sends heartbeat messages every :ref:`replication_timeout <cfg_replication-replication_timeout>` seconds. The master is programmed to disconnect if it does not see acknowledgments of the heartbeat messages within ``replication_timeout`` * 4 seconds.
Если на мастере нет новых данных, требующих репликации, он отправляет на реплики сообщения контрольного сигнала каждые :ref:`replication_timeout <cfg_replication-replication_timeout>` секунд. Мастер запрограммирован на отключение, если он не получает сообщения контрольного сигнала дольше ``replication_timeout`` * 4 секунд.
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/replication/repl_monitoring — Russian

:ref:`idle <box_info_replication_upstream_idle>`: the time (in seconds) since the instance received the last event from a master.
:ref:`бездействие <box_info_replication_upstream_idle>`, время (в секундах) с момента получения последнего события от мастера.
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/replication/repl_monitoring — Russian

The primary indicators of replication health are:
Основные индикаторы работоспособности репликации:
a year ago
Browse all translation changes