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
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 Not available
Last change None
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 86 2,507 18,090
Translated 100% 86 100% 2,507 100% 18,090
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 86 100% 2,507 100% 18,090
Failing checks 6% 6 46% 1,157 43% 7,902
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
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 90 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

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

Trends of last 30 days

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

New source string

testing_project / Documentation: book/admin/troubleshoot — English

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:
a year ago
User avatar None

New source string

testing_project / Documentation: book/admin/troubleshoot — English

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:
a year ago
User avatar None

New source string

testing_project / Documentation: book/admin/troubleshoot — English

The :ref:`transaction processor thread <thread_model>` consumes over 60% CPU.
a year ago
User avatar None

New source string

testing_project / Documentation: book/admin/troubleshoot — English

$ # attaching to a Tarantool instance
$ tt connect <instance_name|URI>
a year ago
User avatar None

New source string

testing_project / Documentation: book/admin/troubleshoot — English

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

New source string

testing_project / Documentation: book/admin/troubleshoot — English

``init.lua``
a year ago
User avatar None

New source string

testing_project / Documentation: book/admin/troubleshoot — English

local fiber = require('fiber')

local worker_next_task = nil
local worker_last_task
local worker_fiber
local worker_cv = fiber.cond()

-- XXX: the module is not ready for reloading, so worker_fiber is
-- respawned when sched.lua is purged from package.loaded.

--
-- Worker is a singleton fiber for not urgent delayed execution of
-- functions. Main purpose - schedule execution of a function,
-- which is going to yield, from a context, where a yield is not
-- allowed. Such as an FFI object's GC callback.
--
local function worker_f()
while true do
local task
while true do
task = worker_next_task
if task then break end
-- XXX: Make the fiber wait until the task is added.
worker_cv:wait()
end
worker_next_task = task.next
task.f(task.arg)
fiber.yield()
end
end

local function worker_safe_f()
pcall(worker_f)
-- The function <worker_f> never returns. If the execution is
-- here, this fiber is probably canceled and now is not able to
-- sleep. Create a new one.
worker_fiber = fiber.new(worker_safe_f)
end

worker_fiber = fiber.new(worker_safe_f)

local function worker_schedule_task(f, arg)
local task = { f = f, arg = arg }
if not worker_next_task then
worker_next_task = task
else
worker_last_task.next = task
end
worker_last_task = task
worker_cv:signal()
end

return {
postpone = worker_schedule_task
}
a year ago
User avatar None

New source string

testing_project / Documentation: book/admin/troubleshoot — English

``sched.lua``
a year ago
User avatar None

New source string

testing_project / Documentation: book/admin/troubleshoot — English

For this purpose, the module called ``sched.lua`` is implemented (see the listing below). It is a part of Tarantool and should be made required in your custom code. The usage example is given in the ``init.lua`` file below.
a year ago
User avatar None

New source string

testing_project / Documentation: book/admin/troubleshoot — English

It is important to note that the finalizer implementations in the examples above increase pressure on the platform performance by creating a new fiber on each ``__gc`` call. To prevent such an excessive fibers spawning, it's better to start a single "scheduler" fiber and provide the interface to postpone the required asynchronous action.
a year ago
Browse all translation changes