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 44% 20 602 4,138 18 1 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-conceptsreplicationrepl_reseed/
File mask locale/*/LC_MESSAGES/concepts/replication/repl_leader_elect.po

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 72 2,356 15,726
Source 36 1,178 7,863
Translated 72% 52 74% 1,754 73% 11,588
Needs editing 2% 2 2% 61 2% 401
Read-only 50% 36 50% 1,178 50% 7,863
Failing checks 2% 2 2% 54 2% 392
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 25% 18 22% 541 23% 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 86 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

2,356
Hosted words
72
Hosted strings
72%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

New alert

testing_project / Documentation: concepts/replication/repl_leader_elect

Component seems unused. 5 months ago
User avatar None

New alert

testing_project / Documentation: concepts/replication/repl_leader_elect

Broken project website URL a year ago
User avatar None

New alert

testing_project / Documentation: concepts/replication/repl_leader_elect

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

Component locked

testing_project / Documentation: concepts/replication/repl_leader_elect

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

New alert

testing_project / Documentation: concepts/replication/repl_leader_elect

Could not merge the repository. a year ago
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
Browse all component changes