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.

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-conceptsreplicationrepl_reseed/
File mask locale/*/LC_MESSAGES/concepts/replication/repl_leader_elect.po
Translation file Download locale/ru/LC_MESSAGES/concepts/replication/repl_leader_elect.po
Last change None
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 36 1,178 7,863
Translated 44% 16 48% 576 47% 3,725
Needs editing 5% 2 5% 61 5% 401
Read-only 0% 0 0% 0 0% 0
Failing checks 2% 1 2% 27 2% 196
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 50% 18 45% 541 47% 3,737
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 42 changes 0 changes 0 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

1,178
Hosted words
36
Hosted strings
44%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

New strings to translate

testing_project / Documentation: concepts/replication/repl_leader_elect — Russian

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

Resource update

testing_project / Documentation: concepts/replication/repl_leader_elect — Russian

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

String updated in the repository

testing_project / Documentation: concepts/replication/repl_leader_elect — Russian

Once noticing the error, a user can choose any representative from each of the sets and inspect the data on them. To correlate the data, the user should remove it from the nodes of one set, and reconnect them to the nodes from the other set that have the correct data.
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: concepts/replication/repl_leader_elect — Russian

Eventually, there will be two sets of nodes with the diverged data, and any node from one set is disconnected from any node from the other set with the ``ER_SPLIT_BRAIN`` error.
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: concepts/replication/repl_leader_elect — Russian

There can still be a situation when a replica set has two leaders working independently (so-called *split-brain*). It can happen, for example, if a user mistakenly lowered the :ref:`replication_synchro_quorum <repl_leader_elect_config>` below ``N / 2 + 1``. In this situation, to preserve the data integrity, if an instance detects the split-brain anomaly in the incoming replication data, it breaks the connection with the instance sending the data and writes the ``ER_SPLIT_BRAIN`` error in the log.
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: concepts/replication/repl_leader_elect — Russian

Fencing applies to the instances that have the :ref:`election_mode <repl_leader_elect_config>` set to "candidate" or "manual".
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: concepts/replication/repl_leader_elect — Russian

In ``strict`` mode, a connection is considered dead if there are no responses for :ref:`2*replication_timeout <cfg_replication-replication_timeout>` seconds on the current leader and for :ref:`4*replication_timeout <cfg_replication-replication_timeout>` seconds on the followers. This improves chances that there is only one leader at any time.
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: concepts/replication/repl_leader_elect — Russian

In ``soft`` mode, a connection is considered dead if there are no responses for :ref:`4*replication_timeout <cfg_replication-replication_timeout>` seconds both on the current leader and the followers.
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: concepts/replication/repl_leader_elect — Russian

The issue is resolved in Tarantool version :doc:`2.10.0 </release/2.10.0>` by introducing the leader *fencing* mode. The mode can be switched by the :ref:`election_fencing_mode <repl_leader_elect_config>` configuration parameter. When the fencing is set to ``soft`` or ``strict``, the leader resigns its leadership if it has less than :ref:`replication_synchro_quorum <repl_leader_elect_config>` of alive connections to the cluster nodes. The resigning leader receives the status of a follower in the current election term and becomes read-only. Leader *fencing* can be turned off by setting the :ref:`election_fencing_mode <repl_leader_elect_config>` configuration parameter to ``off``.
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: concepts/replication/repl_leader_elect — Russian

In the classic Raft algorithm, a leader doesn't track its connectivity to the rest of the cluster. Once the leader is elected, it considers itself in the leader position until receiving a new term from another cluster node. This can lead to a split situation if the other nodes elect a new leader upon losing the connectivity to the previous one.
 
a year ago
Browse all translation changes