Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English 0 0 0 0 0 0 0
Russian 76% 8 208 1,727 3 0 0 0
Please sign in to see the alerts.

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-dev_guideinternalsreplicationreplication_internals/
File mask locale/*/LC_MESSAGES/dev_guide/internals/replication/orphan.po

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 68 1,576 11,458
Source 34 788 5,729
Translated 88% 60 86% 1,368 84% 9,731
Needs editing 7% 5 8% 127 8% 1,017
Read-only 50% 34 50% 788 50% 5,729
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 4% 3 5% 81 6% 710
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 71 changes 1 change 0 changes 0 changes 0 changes 0 changes 4 changes 0 changes
Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb

Quick numbers

1,576
Hosted words
68
Hosted strings
88%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

New alert

testing_project / Documentation: dev_guide/internals/replication/orphan

Component seems unused. 4 months ago
User avatar None

Component unlocked

testing_project / Documentation: dev_guide/internals/replication/orphan

Fixing an alert automatically unlocked the component. a year ago
User avatar None

New alert

testing_project / Documentation: dev_guide/internals/replication/orphan

Broken project website URL a year ago
User avatar None

Component locked

testing_project / Documentation: dev_guide/internals/replication/orphan

The component was automatically locked because of an alert. a year ago
User avatar None

New alert

testing_project / Documentation: dev_guide/internals/replication/orphan

Could not update the repository. a year ago
User avatar None

New strings to translate

testing_project / Documentation: dev_guide/internals/replication/orphan — Russian

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

Resource update

testing_project / Documentation: dev_guide/internals/replication/orphan — Russian

File locale/ru/LC_MESSAGES/dev_guide/internals/replication/orphan.po was added. a year ago
User avatar None

String updated in the repository

testing_project / Documentation: dev_guide/internals/replication/orphan — Russian

Here ``box.cfg{}`` is not being called. The replica connected successfully at some point in the past, and is now ready for an update from the master. But the master cannot provide an update. This can happen by accident, or more likely can happen because the replica is slow (its :ref:`lag <cfg_replication-replication_sync_lag>` is large), and the WAL (.xlog) files containing the updates have been deleted. This is not crippling. The replica can discard what it received earlier, and then ask for the master's latest snapshot (.snap) file contents. Since it is effectively going through the bootstrap process a second time, this is called "rebootstrapping". However, there has to be one difference from an ordinary bootstrap -- the replica's :ref:`replica id <replication-replica-id>` will remain the same. If it changed, then the master would think that the replica is a new addition to the cluster, and would maintain a record of an instance ID of a replica that has ceased to exist. Rebootstrapping was introduced in Tarantool version 1.10.2 and is completely automatic.
Здесь не происходит вызов ``box.cfg{}``. В определенный момент в прошлом реплика успешно установила соединение и в настоящий момент ожидает обновления от мастера. Однако мастер не может передать обновления, что может произойти случайно, или же если реплика работает слишком медленно (большое значение :ref:`lag <cfg_replication-replication_sync_lag>`), а WAL-файлы (.xlog) с обновлениями были удалены. Такая ситуация не является критической -- реплика может сбросить ранее полученные данные, а затем запросить содержание последнего файла снимка (.snap) мастера. Поскольку фактически в таком случае повторно проводится процесс настройки, это называется "повторная настройка". Тем не менее, есть отличие от обычной настройки -- :ref:`идентификатор реплики <replication-replica-id>` останется прежним. Если он изменится, то мастер посчитает, что в кластер добавляется новая реплика, и сохранит идентификатор экземпляра реплики, которой уже не существует. Полностью автоматизированный процесс повторной настройки появился в версии Tarantool 1.10.2.
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: dev_guide/internals/replication/orphan — Russian

**Situation 4: rebootstrap**
**Ситуация 4: повторная настройка**
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: dev_guide/internals/replication/orphan — Russian

If earlier steps succeed, set status to 'running' (master) or 'follow' (replica).
Если предыдущие шаги выполнены, статус изменяется на 'running' (мастер) или 'follow' (реплика).
a year ago
Browse all component changes