* Add ability to log when max_partitions_per_insert_block is reached
There's plenty of reasons to drop max_partitions_per_insert_block
down from it's default of 100, with the main one being even touching
remotely close to this number of partitions will create a lot of
merge activity that can de-stabilise a cluster.
This commit adds the ability to log when the above limit is reached
rather than throw an exception, so that you can gauge the impact on
users when dropping this value down.
* Update docs/ru/operations/settings/query-complexity.md
Co-authored-by: Nikita Taranov <nickita.taranov@gmail.com>
* Update docs/ru/operations/settings/query-complexity.md
Co-authored-by: Nikita Taranov <nickita.taranov@gmail.com>
* Update docs/ru/operations/settings/query-complexity.md
Co-authored-by: Nikita Taranov <nickita.taranov@gmail.com>
---------
Co-authored-by: Nikita Taranov <nickita.taranov@gmail.com>
* DOCSUP-2806: Add meta intro.
* DOCSUP-2806: Update meta intro.
* DOCSUP-2806: Fix meta.
* DOCSUP-2806: Add quotes for meta headers.
* DOCSUP-2806: Remove quotes from meta headers.
* DOCSUP-2806: Add meta headers.
* DOCSUP-2806: Fix quotes in meta headers.
* DOCSUP-2806: Update meta headers.
* DOCSUP-2806: Fix link to nowhere in EN.
* DOCSUP-2806: Fix link (settings to tune)
* DOCSUP-2806: Fix links.
* DOCSUP-2806:Fix links EN
* DOCSUP-2806: Fix build errors.
* DOCSUP-2806: Fix meta intro.
* DOCSUP-2806: Fix toc_priority in examples datasets TOC.
* DOCSUP-2806: Fix items order in toc.
* DOCSUP-2806: Fix order in toc.
* DOCSUP-2806: Fix toc order.
* DOCSUP-2806: Fix order in toc.
* DOCSUP-2806: Fix toc index in create
* DOCSUP-2806: Fix toc order in create.
Co-authored-by: romanzhukov <romanzhukov@yandex-team.ru>
Co-authored-by: alexey-milovidov <milovidov@yandex-team.ru>
The new setting should allow to control query complexity on leaf nodes
excluding the final merging stage on the root-node. For example, distributed
query that reads 1k rows from 5 shards will breach the `max_rows_to_read=5000`,
while effectively every shard reads only 1k rows. With setting `max_rows_to_read_leaf=1500`
this limit won't be reached and query will succeed since every shard reads
not more that ~1k rows.
