mirror of
https://github.com/ClickHouse/ClickHouse.git
synced 2024-11-26 09:32:01 +00:00
Merge pull request #30419 from karnevil13/karnevil-DOCSUP-16354
DOCSUP-16354: Edit and translate to Russian (listen_backlog)
This commit is contained in:
commit
211ff056e9
@ -486,16 +486,12 @@ Backlog (queue size of pending connections) of the listen socket.
|
|||||||
Default value: `4096` (as in linux [5.4+](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19f92a030ca6d772ab44b22ee6a01378a8cb32d4)).
|
Default value: `4096` (as in linux [5.4+](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19f92a030ca6d772ab44b22ee6a01378a8cb32d4)).
|
||||||
|
|
||||||
Usually this value does not need to be changed, since:
|
Usually this value does not need to be changed, since:
|
||||||
- default value is large enough,
|
- default value is large enough,
|
||||||
- and for accepting client's connections server has separate thread.
|
- and for accepting client's connections server has separate thread.
|
||||||
|
|
||||||
So even if you have `TcpExtListenOverflows` (from `nstat`) non zero and this
|
So even if you have `TcpExtListenOverflows` (from `nstat`) non zero and this counter grows for ClickHouse server it does not mean that this value need to be increased, since:
|
||||||
counter grows for ClickHouse server it does not mean that this value need to be
|
- usually if 4096 is not enough it shows some internal ClickHouse scaling issue, so it is better to report an issue.
|
||||||
increased, since:
|
- and it does not mean that the server can handle more connections later (and even if it could, by that moment clients may be gone or disconnected).
|
||||||
- usually if 4096 is not enough it shows some internal ClickHouse scaling
|
|
||||||
issue, so it is better to report an issue.
|
|
||||||
- and it does not mean that the server can handle more connections later (and
|
|
||||||
even if it can, clients can already goes away / disconnect).
|
|
||||||
|
|
||||||
Examples:
|
Examples:
|
||||||
|
|
||||||
|
@ -467,6 +467,26 @@ ClickHouse проверяет условия для `min_part_size` и `min_part
|
|||||||
<listen_host>127.0.0.1</listen_host>
|
<listen_host>127.0.0.1</listen_host>
|
||||||
```
|
```
|
||||||
|
|
||||||
|
## listen_backlog {#server_configuration_parameters-listen_backlog}
|
||||||
|
|
||||||
|
Бэклог (размер очереди соединений, ожидающих принятия) прослушивающего сокета.
|
||||||
|
|
||||||
|
Значение по умолчанию: `4096` (как в linux [5.4+](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19f92a030ca6d772ab44b22ee6a01378a8cb32d4)).
|
||||||
|
|
||||||
|
Обычно это значение незачем менять по следующим причинам:
|
||||||
|
- значение по умолчанию достаточно велико,
|
||||||
|
- для принятия соединения клиента у сервера есть отдельный поток.
|
||||||
|
|
||||||
|
Так что даже если у вас `TcpExtListenOverflows` (из `nstat`) ненулевой и растет для сервера ClickHouse, это не повод увеличивать значение по умолчанию, поскольку:
|
||||||
|
- обычно если 4096 недостаточно, это говорит о внутренних проблемах ClickHouse с масштабированием, так что лучше сообщить о проблеме,
|
||||||
|
- и это не значит, что сервер сможет принять еще больше подключений в дальнейшем (а если и сможет, клиенты, вероятно, уже отсоединятся).
|
||||||
|
|
||||||
|
Примеры:
|
||||||
|
|
||||||
|
``` xml
|
||||||
|
<listen_backlog>4096</listen_backlog>
|
||||||
|
```
|
||||||
|
|
||||||
## logger {#server_configuration_parameters-logger}
|
## logger {#server_configuration_parameters-logger}
|
||||||
|
|
||||||
Настройки логирования.
|
Настройки логирования.
|
||||||
|
@ -28,7 +28,7 @@ stem('language', word)
|
|||||||
Query:
|
Query:
|
||||||
|
|
||||||
``` sql
|
``` sql
|
||||||
SELECT SELECT arrayMap(x -> stem('en', x), ['I', 'think', 'it', 'is', 'a', 'blessing', 'in', 'disguise']) as res;
|
SELECT arrayMap(x -> stem('en', x), ['I', 'think', 'it', 'is', 'a', 'blessing', 'in', 'disguise']) as res;
|
||||||
```
|
```
|
||||||
|
|
||||||
Result:
|
Result:
|
||||||
|
@ -8,10 +8,10 @@ toc_title: "Словарь"
|
|||||||
``` sql
|
``` sql
|
||||||
CREATE DICTIONARY [IF NOT EXISTS] [db.]dictionary_name [ON CLUSTER cluster]
|
CREATE DICTIONARY [IF NOT EXISTS] [db.]dictionary_name [ON CLUSTER cluster]
|
||||||
(
|
(
|
||||||
key1 type1 [DEFAULT|EXPRESSION expr1] [HIERARCHICAL|INJECTIVE|IS_OBJECT_ID],
|
key1 type1 [DEFAULT|EXPRESSION expr1] [IS_OBJECT_ID],
|
||||||
key2 type2 [DEFAULT|EXPRESSION expr2] [HIERARCHICAL|INJECTIVE|IS_OBJECT_ID],
|
key2 type2 [DEFAULT|EXPRESSION expr2],
|
||||||
attr1 type2 [DEFAULT|EXPRESSION expr3],
|
attr1 type2 [DEFAULT|EXPRESSION expr3] [HIERARCHICAL|INJECTIVE],
|
||||||
attr2 type2 [DEFAULT|EXPRESSION expr4]
|
attr2 type2 [DEFAULT|EXPRESSION expr4] [HIERARCHICAL|INJECTIVE]
|
||||||
)
|
)
|
||||||
PRIMARY KEY key1, key2
|
PRIMARY KEY key1, key2
|
||||||
SOURCE(SOURCE_NAME([param1 value1 ... paramN valueN]))
|
SOURCE(SOURCE_NAME([param1 value1 ... paramN valueN]))
|
||||||
|
Loading…
Reference in New Issue
Block a user