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.

Translation status

86 Strings 83%
Browse Translate
2,507 Words 39%

Strings status

86
All strings — 2,507 words Browse Translate Zen
72
Translated strings — 1,000 words Browse Translate Zen
14
Unfinished strings — 1,507 words Browse Translate Zen
10
Untranslated strings — 1,428 words Browse Translate Zen
4
Strings marked for edit — 79 words Browse Translate Zen
14
Unfinished strings without suggestions — 1,507 words Browse Translate Zen
13
Strings with any failing checks — 229 words Browse Translate Zen
11
Translated strings with any failing checks — 207 words Browse Translate Zen
2
Failing check: Unchanged translation — 2 words Browse Translate Zen
1
Failing check: Trailing newline — 12 words Browse Translate Zen
7
Failing check: Double space — 147 words Browse Translate Zen
1
Failing check: Python format — 46 words Browse Translate Zen
1
Failing check: Has been translated — 11 words Browse Translate Zen
2
Failing check: Mismatching line breaks — 23 words Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Documentation: reference/reference_lua/compat/compat_tutorial 0% 36 731 6,164 36 0 0 0
Documentation: concepts/sharding/vshard_architecture 98% 2 42 293 0 3 0 0
Documentation: concepts/replication/repl_reseed 0 0 0 0 0 0 0
Documentation: concepts/engines/memtx 91% 4 287 1,990 0 0 0 0
Documentation: reference/reference_lua/datetime/interval_arithm 0% 29 320 2,155 29 0 0 0
Documentation: concepts/engines/vinyl 99% 1 114 735 0 13 0 0
Documentation: concepts/engines/index 0 0 0 0 0 0 0
Documentation: concepts/sharding/index 90% 1 1 8 1 1 0 0
Documentation: concepts/index 0% 37 581 4,495 37 0 0 0
Documentation: concepts/engines/memtx_vinyl_diff 0 0 0 0 3 0 0
Browse all components

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
Last commit in Weblate Translated using Weblate (Russian) 42f4232d
Weblate Admin authored a year ago
Weblate repository http://weblate.tarantool.io/git/testing_project/documentation-bookadmindaemon_supervision/
File mask locale/*/LC_MESSAGES/book/admin/troubleshoot.po
Translation file Download locale/ru/LC_MESSAGES/book/admin/troubleshoot.po
Last change Oct. 24, 2023, 3:05 p.m.
Last author Weblate Admin

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 86 2,507 18,090
Translated 83% 72 39% 1,000 43% 7,852
Needs editing 4% 4 3% 79 3% 571
Read-only 0% 0 0% 0 0% 0
Failing checks 15% 13 9% 229 10% 1,969
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 11% 10 56% 1,428 53% 9,667
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 104 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

2,507
Hosted words
86
Hosted strings
83%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

New strings to translate

testing_project / Documentation: book/admin/troubleshoot — Russian

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

Resource update

testing_project / Documentation: book/admin/troubleshoot — Russian

The "locale/ru/LC_MESSAGES/book/admin/troubleshoot.po" file was changed. a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/troubleshoot — Russian

local ffi = require('ffi')
local fiber = require('fiber')
local sched = require('sched')

local function __custom_gc(self)
print(("Entered custom GC finalizer for %s... (before yield)"):format(self.a))
fiber.yield()
print(("Leaving custom GC finalizer for %s... (after yield)"):format(self.a))
end

ffi.cdef('struct custom { int a; };')
local custom_t = ffi.metatype('struct custom', {
__gc = function(self)
-- XXX: Do not invoke yielding functions in __gc metamethod.
-- Schedule __custom_gc call via sched.postpone to be run
-- after the execution leaves this routine.
sched.postpone(__custom_gc, self)
print(("Finalization is scheduled for %s..."):format(self.a))
end
})

-- Create several <custom_t> objects to be finalized later.
local t = { }
for i = 1, 10 do t[i] = custom_t(i) end

-- Run full GC cycle to collect the existing garbage. Nothing is
-- going to be printed, since the table <t> is still "alive".
collectgarbage('collect')

-- Remove the reference to the table and, ergo, all references to
-- the objects.
t = nil

-- Run full GC cycle to collect the table and objects inside it.
-- As a result all <custom_t> objects are scheduled for further
-- finalization, but the finalizer itself (i.e. __custom_gc
-- functions) is not called.
collectgarbage('collect')
-- > Finalization is scheduled for 10...
-- > Finalization is scheduled for 9...
-- > ...
-- > Finalization is scheduled for 2...
-- > Finalization is scheduled for 1...

-- XXX: There is no finalization made until the running fiber
-- yields its execution. Let's do it now.
fiber.yield()
-- > Entered custom GC finalizer for 10... (before yield)

-- XXX: Oops, we are here now, since the scheduler fiber yielded
-- the execution to this one. Check this out.
print("We're here now. Let's continue the scheduled finalization.")
-- > We're here now. Let's continue the finalization

-- OK, wait a second to allow the scheduler to cleanup the
-- remaining garbage.
fiber.sleep(1)
-- > Leaving custom GC finalizer for 10... (after yield)
-- > Entered custom GC finalizer for 9... (before yield)
-- > Leaving custom GC finalizer for 9... (after yield)
-- > ...
-- > Entered custom GC finalizer for 1... (before yield)
-- > Leaving custom GC finalizer for 1... (after yield)

print("Did we finish? I guess so.")
-- > Did we finish? I guess so.

-- Stop the instance.
os.exit(0)
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/troubleshoot — Russian

#include <lauxlib.h>
#include <lua.h>
#include <module.h>
#include <stdio.h>

struct custom {
int a;
};

const char *CUSTOM_MTNAME = "CUSTOM_MTNAME";

/*
* XXX: Do not invoke yielding functions in __gc metamethod.
* Create a new fiber to be run after the execution leaves
* this routine. Unfortunately we can't pass the parameters to the
* routine to be executed by the created fiber via <fiber_new_ex>.
* So there is a workaround to load the Lua code below to create
* __gc metamethod passing the object for finalization via Lua
* stack to the spawned fiber.
*/
const char *gc_wrapper_constructor = " local fiber = require('fiber') "
" print('constructor is initialized') "
" return function(__custom_gc) "
" print('constructor is called') "
" return function(self) "
" print('__gc is called') "
" fiber.new(__custom_gc, self) "
" print('Finalization is scheduled') "
" end "
" end "
;

int custom_gc(lua_State *L) {
struct custom *self = luaL_checkudata(L, 1, CUSTOM_MTNAME);
printf("Entered custom_gc for %d... (before yield)\n", self->a);
fiber_sleep(0);
printf("Leaving custom_gc for %d... (after yield)\n", self->a);
return 0;
}

int custom_new(lua_State *L) {
struct custom *self = lua_newuserdata(L, sizeof(struct custom));
luaL_getmetatable(L, CUSTOM_MTNAME);
lua_setmetatable(L, -2);
self->a = lua_tonumber(L, 1);
return 1;
}

static const struct luaL_Reg libcustom_methods [] = {
{ "new", custom_new },
{ NULL, NULL }
};

int luaopen_custom(lua_State *L) {
int rc;

/* Create metatable for struct custom type */
luaL_newmetatable(L, CUSTOM_MTNAME);
/*
* Run the constructor initializer for GC finalizer:
* - load fiber module as an upvalue for GC finalizer
* constructor
* - return GC finalizer constructor on the top of the
* Lua stack
*/
rc = luaL_dostring(L, gc_wrapper_constructor);
/*
* Check whether constructor is initialized (i.e. neither
* syntax nor runtime error is raised).
*/
if (rc != LUA_OK)
luaL_error(L, "test module loading failed: constructor init");
/*
* Create GC object for <custom_gc> function to be called
* in scope of the GC finalizer and push it on top of the
* constructor returned before.
*/
lua_pushcfunction(L, custom_gc);
/*
* Run the constructor with <custom_gc> GCfunc object as
* a single argument. As a result GC finalizer is returned
* on the top of the Lua stack.
*/
rc = lua_pcall(L, 1, 1, 0);
/*
* Check whether GC finalizer is created (i.e. neither
* syntax nor runtime error is raised).
*/
if (rc != LUA_OK)
luaL_error(L, "test module loading failed: __gc init");
/*
* Assign the returned function as a __gc metamethod to
* custom type metatable.
*/
lua_setfield(L, -2, "__gc");

/*
* Initialize Lua table for custom module and fill it
* with the custom methods.
*/
lua_newtable(L);
luaL_register(L, NULL, libcustom_methods);
return 1;
}
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/troubleshoot — Russian

local ffi = require('ffi')
local fiber = require('fiber')

ffi.cdef('struct custom { int a; };')

local function __custom_gc(self)
print(("Entered custom GC finalizer for %s... (before yield)"):format(self.a))
fiber.yield()
print(("Leaving custom GC finalizer for %s... (after yield)"):format(self.a))
end

local custom_t = ffi.metatype('struct custom', {
__gc = function(self)
-- XXX: Do not invoke yielding functions in __gc metamethod.
-- Create a new fiber to run after the execution leaves
-- this routine.
fiber.new(__custom_gc, self)
print(("Finalization is scheduled for %s..."):format(self.a))
end
})

-- Create a cdata object of <custom_t> type.
local c = custom_t(42)

-- Remove a single reference to that object to make it subject
-- for GC.
c = nil

-- Run full GC cycle to purge the unreferenced object.
collectgarbage('collect')
-- > Finalization is scheduled for 42...

-- XXX: There is no finalization made until the running fiber
-- yields its execution. Let's do it now.
fiber.yield()
-- > Entered custom GC finalizer for 42... (before yield)
-- > Leaving custom GC finalizer for 42... (after yield)
 
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/troubleshoot — Russian

This parameter can be changed on the fly, so you don't need to restart Tarantool. Attach to the Tarantool instance with :ref:`tt <tt-cli>` utility and call ``box.cfg{}`` with a new ``readahead`` value:
Перезапускать Tarantool при этом не требуется. Для обновления конфигурации необходимо подключиться к Tarantool с помощью утилиты :ref:`tarantoolctl <tarantoolctl>` и передать в ``box.cfg{}`` новое значение параметра ``readahead``:
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/troubleshoot — Russian

Attach to the Tarantool instance with :ref:`tt <tt-cli>` utility, analyze the query statistics with :doc:`box.stat() </reference/reference_lua/box_stat>` and spot the CPU consumption leader. The following commands can help:
Подключиться к Tarantool с помощью утилиты :ref:`tarantoolctl <tarantoolctl>`, внимательно изучить статистику запросов с помощью :doc:`box.stat() </reference/reference_lua/box_stat>` и выявить источник потребления. Для этой цели могут оказаться полезными следующие команды:
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/troubleshoot — Russian

The :ref:`transaction processor thread <thread_model>` consumes over 60% CPU.
:ref:`Поток обработки транзакций <atomic-threads_fibers_yields>` нагружает ЦП более чем на 60%.
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/troubleshoot — Russian

In versions of Tarantool before 1.10, the server needs to be restarted to change this parameter. The Tarantool server will be unavailable while restarting from .xlog files, unless you restart it using :ref:`hot standby <index-hot_standby>` mode. In the latter case, nearly 100% server availability is guaranteed.
В версиях Tarantool до 1.10 для изменения данного параметра требуется перезагрузить сервер. При обычной перезагрузке сервер будет недоступен на время старта Tarantool из .xlog-файлов. При перезагрузке в режиме горячего резервирования :ref:`hot standby <index-hot_standby>` гарантирована практически 100%-ная доступность.
a year ago
User avatar None

String updated in the repository

testing_project / Documentation: book/admin/troubleshoot — Russian

$ # attaching to a Tarantool instance
$ tt connect <instance_name|URI>
$ # подключаемся к админ-консоли нужного экземпляра
$ tarantoolctl enter <instance_name>
$ # -- ИЛИ --
$ tarantoolctl connect <URI>
a year ago
Browse all translation changes