Skip to content

Provide better partitions hint for merge selecting task#49637

Merged
tavplubix merged 9 commits intomasterfrom
less_zookeeper_requests
May 23, 2023
Merged

Provide better partitions hint for merge selecting task#49637
tavplubix merged 9 commits intomasterfrom
less_zookeeper_requests

Conversation

@tavplubix
Copy link
Copy Markdown
Member

@tavplubix tavplubix commented May 7, 2023

Changelog category (leave one):

  • Improvement

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

Reduced number of List ZooKeeper requests when selecting parts to merge and a lot of partitions do not have anything to merge

Also fixes #49201

@robot-clickhouse-ci-2 robot-clickhouse-ci-2 added the pr-improvement Pull request with some product improvements label May 7, 2023
@robot-clickhouse-ci-2
Copy link
Copy Markdown
Contributor

robot-clickhouse-ci-2 commented May 7, 2023

This is an automated comment for commit c2b1e8c with description of existing statuses. It's updated for the latest CI running
The full report is available here
The overall status of the commit is 🔴 failure

Check nameDescriptionStatus
AST fuzzerRuns randomly generated queries to catch program errors. The build type is optionally given in parenthesis. If it fails, ask a maintainer for help🟢 success
CI runningA meta-check that indicates the running CI. Normally, it's in success or pending state. The failed status indicates some problems with the PR🟡 pending
ClickHouse build checkBuilds ClickHouse in various configurations for use in further steps. You have to fix the builds that fail. Build logs often has enough information to fix the error, but you might have to reproduce the failure locally. The cmake options can be found in the build log, grepping for cmake. Use these options and follow the general build process🟢 success
Compatibility checkChecks that clickhouse binary runs on distributions with old libc versions. If it fails, ask a maintainer for help🟢 success
Docker image for serversThe check to build and optionally push the mentioned image to docker hub🟢 success
Fast testNormally this is the first check that is ran for a PR. It builds ClickHouse and runs most of stateless functional tests, omitting some. If it fails, further checks are not started until it is fixed. Look at the report to see which tests fail, then reproduce the failure locally as described here🟢 success
Flaky testsChecks if new added or modified tests are flaky by running them repeatedly, in parallel, with more randomization. Functional tests are run 100 times with address sanitizer, and additional randomization of thread scheduling. Integrational tests are run up to 10 times. If at least once a new test has failed, or was too long, this check will be red. We don't allow flaky tests, read the doc🟢 success
Install packagesChecks that the built packages are installable in a clear environment🟢 success
Integration testsThe integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests🔴 failure
Mergeable CheckChecks if all other necessary checks are successful🟢 success
Performance ComparisonMeasure changes in query performance. The performance test report is described in detail here. In square brackets are the optional part/total tests🟢 success
Push to DockerhubThe check for building and pushing the CI related docker images to docker hub🟢 success
SQLancerFuzzing tests that detect logical bugs with SQLancer tool🟢 success
SqllogicRun clickhouse on the sqllogic test set against sqlite and checks that all statements are passed🟢 success
Stateful testsRuns stateful functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc🟢 success
Stateless testsRuns stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc🟢 success
Stress testRuns stateless functional tests concurrently from several clients to detect concurrency-related errors🟢 success
Style CheckRuns a set of checks to keep the code style clean. If some of tests failed, see the related log from the report🟢 success
Unit testsRuns the unit tests for different release types🟢 success
Upgrade checkRuns stress tests on server version from last release and then tries to upgrade it to the version from the PR. It checks if the new server can successfully startup without any errors, crashes or sanitizer asserts🟢 success

@tavplubix tavplubix force-pushed the less_zookeeper_requests branch from 3bc16e2 to aa829c4 Compare May 8, 2023 22:23
@tavplubix tavplubix marked this pull request as ready for review May 9, 2023 21:30
@tavplubix
Copy link
Copy Markdown
Member Author

Integration tests (asan) [4/6] - #45404
Stateless tests (release, DatabaseReplicated) [3/4] - 02439_merge_selecting_partitions - something weird, will check later
Stateless tests (release, analyzer) - 02458_relax_too_many_parts is broken in master

@tavplubix
Copy link
Copy Markdown
Member Author

Stateless tests (release, analyzer) - #46835 (comment)
Unit tests (asan) - IOResourceDynamicResourceManager was broken in master

@antonio2368 antonio2368 self-assigned this May 19, 2023
Comment on lines +254 to +258
auto new_end_it = std::remove_if(res.begin(), res.end(), [partitions_hint](const auto & part)
{
return !partitions_hint->contains(part->info.partition_id);
});
res.erase(new_end_it, res.end());
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


/// Lightweight version of ReplicatedMergeTreeMergePredicate that do not make any ZooKeeper requests,
/// but may return false-positive results. Checks only a subset of required conditions.
class TrivialMergePredicate
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LocalMergePredicate maybe?

@@ -0,0 +1,24 @@

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

drop table if exists rmt

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think these drop queries are really useful since we create a new database for each test, but okay

@tavplubix tavplubix force-pushed the less_zookeeper_requests branch from 087dfba to c2b1e8c Compare May 22, 2023 17:30
@tavplubix
Copy link
Copy Markdown
Member Author

Integration tests (release) [2/4] - #48691

@boldakovds
Copy link
Copy Markdown

@tavplubix Hi! Can you backport this to 23.3 ? It will be really helpful for us.

@Algunenano
Copy link
Copy Markdown
Member

Hi! Can you backport this to 23.3 ? It will be really helpful for us.

Improvements, and specially ones with critical changes like this, aren't backported. That's the whole point of stable releases. Consider upgrading.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-improvement Pull request with some product improvements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

optimize fail when no data in partition in replicated table

5 participants