The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not merge the repository.
Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English 0 0 0 0 1 0 0
Russian 39% 14 504 3,479 5 4 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
Last remote commit updated pot afee6c42
TarantoolBot authored a year ago
Weblate repository http://weblate.tarantool.io/git/testing_project/documentation-how-toreplicationrepl_remove_instances/
File mask locale/*/LC_MESSAGES/how-to/replication/repl_leader_elect.po

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 46 1,270 8,884
Source 23 635 4,442
Translated 69% 32 60% 766 60% 5,405
Needs editing 19% 9 33% 430 33% 2,961
Read-only 50% 23 50% 635 50% 4,442
Failing checks 10% 5 3% 45 4% 389
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 10% 5 5% 74 5% 518
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 74 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 2 changes 0 changes
Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb

Quick numbers

1,270
Hosted words
46
Hosted strings
69%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

New alert

testing_project / Documentation: how-to/replication/repl_leader_elect

Component seems unused. 5 months ago
User avatar None

New alert

testing_project / Documentation: how-to/replication/repl_leader_elect

Broken project website URL a year ago
User avatar None

New alert

testing_project / Documentation: how-to/replication/repl_leader_elect

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

Component locked

testing_project / Documentation: how-to/replication/repl_leader_elect

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

New alert

testing_project / Documentation: how-to/replication/repl_leader_elect

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

New strings to translate

testing_project / Documentation: how-to/replication/repl_leader_elect — Russian

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

Resource update

testing_project / Documentation: how-to/replication/repl_leader_elect — Russian

The "locale/ru/LC_MESSAGES/how-to/replication/repl_leader_elect.po" file was changed. a year ago
User avatar None

String updated in the repository

testing_project / Documentation: how-to/replication/repl_leader_elect — Russian

Also, the automated leader election doesn't bring many benefits in terms of data safety when used *without* :ref:`synchronous replication <repl_sync>`. If the replication is asynchronous and a new leader gets elected, the old leader is still active and considers itself the leader. In such case, nothing stops it from accepting requests from clients and making transactions. Non-synchronous transactions are successfully committed because they are not checked against the quorum of replicas. Synchronous transactions fail because they are not able to collect the quorum -- most of the replicas reject these old leader's transactions since it is not a leader anymore.
Если использовать автоматические выборы лидера *без* :ref:`синхронной репликации <repl_sync>`, может наступить рассогласование данных. При асинхронной репликации успешные выборы нового лидера не означают, что прежний лидер немедленно сложит с себя полномочия. Он по-прежнему будет считать себя активным лидером, принимать запросы от клиентов и совершать транзакции. Асинхронные транзакции, минуя кворум реплик, будут успешно проходить коммиты. При этом синхронные транзакции будут приводить к ошибке, поскольку для их коммита не удастся собрать кворум: большинство реплик будут отвергать транзакции, передаваемые прежним лидером, поскольку уже был избран новый.
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: how-to/replication/repl_leader_elect — Russian

For example, suppose there are five nodes. When the quorum is set to ``2``, ``node1`` and ``node2`` can both vote for ``node1``. ``node3`` and ``node4`` can both vote for ``node5``. In this case, ``node1`` and ``node5`` both win the election. When the quorum is set to the cluster majority, that is ``(<cluster size> / 2) + 1`` or greater, the split vote is impossible.
Допустим, есть пять узлов. Если значение кворума — ``2``, то ``node1`` и ``node2`` оба могут проголосовать за ``node1``. При этом ``node3`` и ``node4`` оба могут проголосовать за ``node5``. Тогда выборы выиграют и ``node1``, и ``node5``. Но если в качестве значения кворума установлено большинство, то есть ``(<размер кластера> / 2) + 1`` или больше, то разделение голосов поровну невозможно.
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: how-to/replication/repl_leader_elect — Russian

Leader election doesn't work correctly if the election quorum is set to less or equal than ``<cluster size> / 2`` because in that case, a split vote can lead to a state when two leaders are elected at once.
Механизм выборов лидера не будет корректно работать, если кворум меньше ``<размер кластера> / 2`` или равен этому значению, поскольку в этом случае два лидера могут быть избраны одновременно.
a year ago
Browse all component changes