This can be useful for debugging and for testing (since you will not
need to obtain query_id and look at query_log).
v2:
- mark test as long
- add option to docs
- add type of profile event into logs too
v3:
- resolve conflicts
- and fix onProfileEvents callback
v4:
- add --print-profile-events separate switch
Changelog:
- Verify that all rows was read in MergeTreeReaderWide
- Ignore some exceptions for Wide parts
- Take max_rows_to_read into account
- Verify that requested rows is not zero (otherwise it is too tricky)
- Simply verify that buffer is not empty
* Перевод без изменений содержания
* в ру-версию добавлены ngrambf_v1 и tokenbf_v1
* Update mergetree.md
* Update docs/ru/operations/settings/settings.md
Co-authored-by: olgarev <56617294+olgarev@users.noreply.github.com>
* Update docs/ru/operations/settings/settings.md
Co-authored-by: olgarev <56617294+olgarev@users.noreply.github.com>
* Update docs/ru/operations/settings/settings.md
Co-authored-by: olgarev <56617294+olgarev@users.noreply.github.com>
* Update docs/ru/operations/settings/settings.md
Co-authored-by: olgarev <56617294+olgarev@users.noreply.github.com>
* Update docs/ru/operations/settings/settings.md
Co-authored-by: olgarev <56617294+olgarev@users.noreply.github.com>
* Update docs/ru/engines/table-engines/mergetree-family/mergetree.md
Co-authored-by: olgarev <56617294+olgarev@users.noreply.github.com>
* Update docs/ru/engines/table-engines/mergetree-family/mergetree.md
Co-authored-by: olgarev <56617294+olgarev@users.noreply.github.com>
* Update docs/ru/engines/table-engines/mergetree-family/mergetree.md
Co-authored-by: olgarev <56617294+olgarev@users.noreply.github.com>
* Corrections and translation
* in EN ver. lines 349-351 were included into the codeblock -- moved them to the proper place
* ...
Co-authored-by: olgarev <56617294+olgarev@users.noreply.github.com>
Set --server-check-retries to 90 (and this is ~45 seconds), since right
now sometimes it is not enough [1].
[1]: https://clickhouse-test-reports.s3.yandex.net/30191/0e34a9d550cfe6924fe575871f36c44dd44acdaa/functional_stateless_tests_(memory).html#fail1
And the reason I guess is clickhouse-test had been rewritten to
http.client in #30065, and since now it does not need to execute
clickhouse-client binary, which in debug/sanitizers builds can take also
sometime.
That said that with clickhouse-client for hung check it was not 15
seconds, but more (each clickhouse-client requires 0.6sec with
sanitizers for simple SELECT 1, while w/o 0.1second, also too much
should be optimized)
