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-bookadminupgrades2110/
File mask locale/*/LC_MESSAGES/book/admin/upgrades/1.6-1.10.po
Translation file Download locale/ru/LC_MESSAGES/book/admin/upgrades/1.6-1.10.po
Last change None
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 23 698 4,664
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 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 100% 23 100% 698 100% 4,664
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 25 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

698
Hosted words
23
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: book/admin/upgrades/1.6-1.10 — Russian

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

Resource update

testing_project / Documentation: book/admin/upgrades/1.6-1.10 — Russian

File locale/ru/LC_MESSAGES/book/admin/upgrades/1.6-1.10.po was added. a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/upgrades/1.6-1.10 — Russian

**Taking snapshots (step 6):** The user might be concerned with snapshot size in 1.10 -- it's drastically smaller than the one created by 1.6 (for example, ~300 Mb vs. 6 Gb in some corner cases). There is nothing to worry about. Tarantool 1.6 didn't compress snapshots, while Tarantool 1.10 and above does that.
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/upgrades/1.6-1.10 — Russian

-- First find all spaces containing unsigned fields with non-unsigned values in them.
-- Say, we have one such space denoted problematic_space and the problem is in field problematic_field_no.
a = box.space.problematic_space:format()
a[problematic_field_no].type = 'number'
box.space.problematic_space:format(a)
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/upgrades/1.6-1.10 — Russian

**Running box.schema.upgrade() (step 5):** There was a breaking change between 1.6 and 1.10 -- in 1.6, the field type ``num`` was an alias to ``number``, and in 1.10, ``num`` is converted to ``unsigned``. This means that after ``box.schema.upgrade()`` is performed on the master, the user might have some spaces with ``unsigned`` fields containing non-unsigned values: ``double``, ``int``, and so on. This will make the snapshot inconsistent, unless an extra action is performed after ``box.schema.upgrade()``. Run this code in the Tarantool console on the new master:
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/upgrades/1.6-1.10 — Russian

**Restarting on the target version (steps 1, 2, and 4):** Tarantool 1.10+ fails to recover from 1.6 xlogs, unless ``box.cfg{force_recovery = true}`` is set. There is a slight difference between 1.6 and 1.10 xlogs, which makes 1.6 xlogs appear erroneous to 1.10+ instances. In order to work around this, start the instance in ``force_recovery`` mode. To do so, add the line ``force_recovery = true`` to the file where the instance is initialized -- for example, to ``init.lua``.
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/upgrades/1.6-1.10 — Russian

**Point of no return:** When upgrading from Tarantool 1.6, the step 3 (switching the master) is the point of no return. Оnce you complete it, **the schema is no longer compatible with the initial version**.
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/upgrades/1.6-1.10 — Russian

old_repl = box.cfg.replication
box.cfg{replication = ""}
box.cfg{replication = old_repl}
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/upgrades/1.6-1.10 — Russian

**Replication check:** New Tarantool nodes follow 1.6 nodes just fine, but some 1.6 nodes might disconnect from new nodes with an ER_LOADING error. This is not critical, the error goes away when replication on 1.6 is restarted:
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/upgrades/1.6-1.10 — Russian

1.6 storage upgrade specifics
 
a year ago
Browse all translation changes