-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop helping tables when the whole table is done in clickhouse-copier #19743
Conversation
478e823
to
1507caa
Compare
I'm confused why |
1507caa
to
d5ba2e3
Compare
@nikitamikhaylov PTAL. |
d5ba2e3
to
113a03b
Compare
113a03b
to
198a8d3
Compare
Our AST Fuzzer processes all test queries for each commits, not only yours or related to this PR. That's why it fails. The true way to deal with it is to find the query on which ClickHouse crashes, validate it and submit an issue with tag |
…done in clickhouse-copier
… done in clickhouse-copier
… done in clickhouse-copier
…done in clickhouse-copier
Backport #19743 to 21.2: Drop helping tables when the whole table is done in clickhouse-copier
Backport #19743 to 20.12: Drop helping tables when the whole table is done in clickhouse-copier
Backport #19743 to 21.1: Drop helping tables when the whole table is done in clickhouse-copier
Backport #19743 to 20.11: Drop helping tables when the whole table is done in clickhouse-copier
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Fix a bug that moving pieces to destination table may failed in case of launching multiple clickhouse-copiers.
Detailed description / Documentation draft:
When launching multiple clickhouse-copiers, the one moving pieces to destination table may spend long time. However, before it finished, the others had executed
tryProcessTable()
beyondmax_table_tries
times, and then all the piece tables had been dropped. As a result, the pieces moving failed.@alexey-milovidov