Zen

Translation

English
$ export LISTEN_URI=3301
$ ~/tarantool/src/tarantool script.lua ARG
... main/101/script.lua C> Tarantool 2.8.3-0-g01023dbc2
... main/101/script.lua C> log level 5
... main/101/script.lua I> mapping 33554432 bytes for memtx tuple arena...
... main/101/script.lua I> recovery start
... main/101/script.lua I> recovering from './00000000000000000000.snap'
... main/101/script.lua I> set 'listen' configuration option to "3301"
... main/102/leave_local_hot_standby I> ready to accept requests
Starting ARG
... main C> entering the event loop
520/5380 · 538
English Russian Actions
Using the ``?`` delimiter when URIs are specified in a string format.
 
box.cfg { listen = "127.0.0.1:3301?p1=value1&p2=value2, /unix.sock?p3=value3" }
 
Using the ``params`` table: a URI is passed in a table with additional parameters in the "params" table. Parameters in the "params" table overwrite the ones from a URI string ("value2" overwrites "value1" for ``p1`` in the example below).
 
box.cfg { listen = {
"127.0.0.1:3301?p1=value1",
params = {p1 = "value2", p2 = "value3"}
}
}
 
Using the ``default_params`` table for specifying default parameter values.
 
In the example below, two URIs are passed in a table. The default value for the ``p3`` parameter is defined in the ``default_params`` table and used if this parameter is not specified in URIs. Parameters in the ``default_params`` table are applicable to all the URIs passed in a table.
 
box.cfg { listen = {
"127.0.0.1:3301?p1=value1",
{ uri = "/unix.sock", params = { p2 = "value2" } },
default_params = { p3 = "value3" }
}
}
 
The recommended way for specifying URI with additional parameters is the following:
 
box.cfg { listen = {
{uri = "127.0.0.1:3301", params = {p1 = "value1"}},
{uri = "/unix.sock", params = {p2 = "value2"}},
{uri = 3302, params = {p3 = "value3"}}
}
}
 
In case of a single URI, the following syntax also works:
 
box.cfg { listen = {
uri = "127.0.0.1:3301",
params = { p1 = "value1", p2 = "value2" }
}
}
 
Initialization file
Файл инициализации
If the command to start Tarantool includes :codeitalic:`lua-initialization-file`, then Tarantool begins by invoking the Lua program in the file, which by convention may have the name "``script.lua``". The Lua program may get further arguments from the command line or may use operating-system functions, such as ``getenv()``. The Lua program almost always begins by invoking ``box.cfg()``, if the database server will be used or if ports need to be opened. For example, suppose ``script.lua`` contains the lines
Если команда запуска Tarantool включает в себя :codeitalic:`файл инициализации`, то Tarantool запустится посредством вызова Lua-программы из этого файла, который обычно называется "``script.lua``". В Lua-программу можно добавить дополнительные аргументы из командной строки или функции операционной системы, такие как ``getenv()``. Lua-программа практически всегда запускается посредством вызова ``box.cfg()``, если будет использоваться сервер базы данных или же необходимо открыть порты. Например, предположим, что файл ``script.lua`` содержит строки:
#!/usr/bin/env tarantool
box.cfg{
listen = os.getenv("LISTEN_URI"),
memtx_memory = 33554432,
pid_file = "tarantool.pid",
wal_max_size = 2500
}
print('Starting ', arg[1])
#!/usr/bin/env tarantool
box.cfg{
listen = os.getenv("LISTEN_URI"),
memtx_memory = 100000,
pid_file = "tarantool.pid",
wal_max_size = 2500
}
print('Starting ', arg[1])
and suppose the environment variable LISTEN_URI contains 3301, and suppose the command line is ``~/tarantool/src/tarantool script.lua ARG``. Then the screen might look like this:
и предположим, что переменная окружения LISTEN_URI содержит значение 3301, а также предположим, что в командной строке ``~/tarantool/src/tarantool script.lua ARG``. Тогда вывод на экране может выглядеть следующим образом:
$ export LISTEN_URI=3301
$ ~/tarantool/src/tarantool script.lua ARG
... main/101/script.lua C> Tarantool 2.8.3-0-g01023dbc2
... main/101/script.lua C> log level 5
... main/101/script.lua I> mapping 33554432 bytes for memtx tuple arena...
... main/101/script.lua I> recovery start
... main/101/script.lua I> recovering from './00000000000000000000.snap'
... main/101/script.lua I> set 'listen' configuration option to "3301"
... main/102/leave_local_hot_standby I> ready to accept requests
Starting ARG
... main C> entering the event loop
$ export LISTEN_URI=3301
$ ~/tarantool/src/tarantool script.lua ARG
... main/101/script.lua C> version 1.7.0-1216-g73f7154
... main/101/script.lua C> log level 5
... main/101/script.lua I> mapping 107374184 bytes for a shared arena...... main/101/script.lua I> recovery start
... main/101/script.lua I> recovering from './00000000000000000000.snap'... main/101/script.lua I> primary: bound to 0.0.0.0:3301
... main/102/leave_local_hot_standby I> ready to accept requests
Starting ARG
... main C> entering the event loop
If you wish to start an interactive session on the same terminal after initialization is complete, you can use :ref:`console.start() <console-start>`.
Если необходимо начать интерактивную сессию на том же терминале по окончании инициализации, можно использовать :ref:`console.start() <console-start>`.
Configuration parameters
Конфигурационные параметры
Configuration parameters have the form:
Конфигурационные параметры выглядят так:
:extsamp:`{**{box.cfg}**}{[{*{key = value}*} [, {*{key = value ...}*}]]}`
:extsamp:`{**{box.cfg}**}{[{*{ключ = значение}*} [, {*{ключ = значение ...}*}]]}`
Since ``box.cfg`` may contain many configuration parameters and since some of the parameters (such as directory addresses) are semi-permanent, it's best to keep ``box.cfg`` in a Lua file. Typically this Lua file is the initialization file which is specified on the Tarantool command line.
Поскольку в ``box.cfg`` может быть множество конфигурационных параметров, а некоторые параметры (такие как адреса директорий) являются полупостоянными, лучше всего хранить ``box.cfg`` в Lua-файле. Как правило, такой Lua-файл представляет собой файл инициализации, который указан в командной строке Tarantool.
Most configuration parameters are for allocating resources, opening ports, and specifying database behavior. All parameters are optional. A few parameters are dynamic, that is, they can be changed at runtime by calling ``box.cfg{}`` a second time. For example, the command below sets the :ref:`listen port <cfg_basic-listen>` to ``3301``.
Большинство конфигурационных параметров предназначены для распределения ресурсов, открытия портом и указания поведения базы данных. Все параметры необязательны. Некоторые параметры динамичны, то есть могут изменяться во время исполнения кода посредством повторного вызова ``box.cfg{}``.
tarantool> box.cfg{ listen = 3301 }
2023-05-10 13:28:54.667 [31326] main/103/interactive I> tx_binary: stopped
2023-05-10 13:28:54.667 [31326] main/103/interactive I> tx_binary: bound to [::]:3301
2023-05-10 13:28:54.667 [31326] main/103/interactive/box.load_cfg I> set 'listen' configuration option to 3301
---
...
 
To see all the non-null parameters, execute ``box.cfg`` (no parentheses).
 
tarantool> box.cfg
---
- replication_skip_conflict: false
wal_queue_max_size: 16777216
feedback_host: https://feedback.tarantool.io
memtx_dir: .
memtx_min_tuple_size: 16
-- other parameters --
...
 
To see a particular parameter value, call a corresponding ``box.cfg`` option. For example, ``box.cfg.listen`` shows the specified :ref:`listen address <cfg_basic-listen>`.
 
tarantool> box.cfg.listen
---
- 3301
...
tarantool> box.info.vclock
---
- {0: 10, 1: 4}
...
Methods of setting and priorities
 
Tarantool configuration parameters can be specified in different ways. The priority of parameter sources is the following, from higher to lower:
 
``box.cfg`` options
 
:ref:`environment variables <box-cfg-params-env>`
 

Loading…

User avatar None

String updated in the repository

testing_project / Documentation: reference/configuration/index — Russian

$ export LISTEN_URI=3301
$ ~/tarantool/src/tarantool script.lua ARG
... main/101/script.lua C> Tarantool 2.8.3-0-g01023dbc2
... main/101/script.lua C> log level 5
... main/101/script.lua I> mapping 33554432 bytes for memtx tuple arena...
... main/101/script.lua I> recovery start
... main/101/script.lua I> recovering from './00000000000000000000.snap'
... main/101/script.lua I> set 'listen' configuration option to "3301"
... main/102/leave_local_hot_standby I> ready to accept requests
Starting ARG
... main C> entering the event loop
$ export LISTEN_URI=3301
$ ~/tarantool/src/tarantool script.lua ARG
... main/101/script.lua C> version 1.7.0-1216-g73f7154
... main/101/script.lua C> log level 5
... main/101/script.lua I> mapping 107374184 bytes for a shared arena...... main/101/script.lua I> recovery start
... main/101/script.lua I> recovering from './00000000000000000000.snap'... main/101/script.lua I> primary: bound to 0.0.0.0:3301
... main/102/leave_local_hot_standby I> ready to accept requests
Starting ARG
... main C> entering the event loop
a year ago
Browse all string changes

Things to check

Mismatching line breaks

Number of new lines in translation does not match source

Reset

Glossary

English Russian
No related strings found in the glossary.

String information

String age
a year ago
Last updated
a year ago
Source string age
a year ago
Translation file
locale/ru/LC_MESSAGES/reference/configuration/index.po, string 74