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/replication_server_startup.po
Translation file Download locale/ru/LC_MESSAGES/dev_guide/internals/replication/replication_server_startup.po
Last change None
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 18 949 5,872
Translated 0% 0 0% 0 0% 0
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 11% 2 16% 154 15% 896
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 100% 18 100% 949 100% 5,872
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 20 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

949
Hosted words
18
Hosted strings
0%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

New strings to translate

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

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

Resource update

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

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

String updated in the repository

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

The maximum number of entries in the ``_cluster`` space is :ref:`32 <limitations_replicas>`. Tuples for out-of-date replicas are not automatically re-used, so if this 32-replica limit is reached, users may have to reorganize the ``_cluster`` space manually.
 
a year ago
User avatar None

String updated in the repository

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

The following limitation still applies for the current Tarantool version:
 
a year ago
User avatar None

String updated in the repository

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

The replicas of a replica set should be started up at slightly different times. This is not mandatory but prevents a situation where each replica is waiting for the other replica to be ready.
 
a year ago
User avatar None

String updated in the repository

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

The URIs in the ``replication`` parameter should all be in the same order on all replicas. This is not mandatory but is an aid to consistency.
 
a year ago
User avatar None

String updated in the repository

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

The following temporary limitations applied for Tarantool versions earlier than 1.7.7:
 
a year ago
User avatar None

String updated in the repository

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

*If there is a snapshot file and replication source is not empty*: |br| first the local replica goes through the recovery process described in the previous section, using its own .snap and .xlog files. Then it sends a "subscribe" request to all the other replicas of the replica set. The subscribe request contains the server vector clock. The vector clock has a collection of pairs 'server id, lsn' for every replica in the ``_cluster`` system space. Each distant replica, upon receiving a subscribe request, will read its .xlog files' requests and send them to the local replica if (lsn of .xlog file request) is greater than (lsn of the vector clock in the subscribe request). After all the other replicas of the replica set have responded to the local replica's subscribe request, the replica startup is complete.
 
a year ago
User avatar None

String updated in the repository

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

In the end, the local replica knows what replica set it belongs to, the distant replica knows that the local replica is a member of the replica set, and both replicas have the same database contents.
 
a year ago
User avatar None

String updated in the repository

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

the distant replica looks for a record of the connecting instance in its ``_cluster`` space. If there is none, then the handshake fails. |br| Otherwise the handshake is successful. The distant replica will read any new information from its own .snap and .xlog files, and send the new requests to the local replica.
 
a year ago
Browse all translation changes