Skip to content

Added cache for primary index#72102

Merged
alesapin merged 8 commits intoClickHouse:masterfrom
CurtizJ:primary-index-cache
Nov 26, 2024
Merged

Added cache for primary index#72102
alesapin merged 8 commits intoClickHouse:masterfrom
CurtizJ:primary-index-cache

Conversation

@CurtizJ
Copy link
Copy Markdown
Member

@CurtizJ CurtizJ commented Nov 19, 2024

Changelog category (leave one):

  • New Feature

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

Added cache for primary index of MergeTree tables (can be enabled by table setting use_primary_key_cache). If lazy load and cache are enabled for primary index, it will be loaded to cache on demand (similar to mark cache) instead of keeping it in memory forever. Added prewarm of primary index on inserts/mergs/fetches of data parts and on restarts of table (can be enabled by setting prewarm_primary_key_cache).

Resolves #71992.

Documentation entry for user-facing changes

  • Documentation is written (mandatory for new features)

CI Settings (Only check the boxes if you know what you are doing):

  • Allow: All Required Checks
  • Allow: Stateless tests
  • Allow: Stateful tests
  • Allow: Integration Tests
  • Allow: Performance tests
  • Allow: All Builds
  • Allow: batch 1, 2 for multi-batch jobs
  • Allow: batch 3, 4, 5, 6 for multi-batch jobs

  • Exclude: Style check
  • Exclude: Fast test
  • Exclude: All with ASAN
  • Exclude: All with TSAN, MSAN, UBSAN, Coverage
  • Exclude: All with aarch64, release, debug

  • Run only fuzzers related jobs (libFuzzer fuzzers, AST fuzzers, etc.)
  • Exclude: AST fuzzers

  • Do not test
  • Woolen Wolfdog
  • Upload binaries for special builds
  • Disable merge-commit
  • Disable CI cache

@robot-ch-test-poll3 robot-ch-test-poll3 added the pr-feature Pull request with new product feature label Nov 19, 2024
@robot-ch-test-poll4
Copy link
Copy Markdown
Contributor

robot-ch-test-poll4 commented Nov 19, 2024

This is an automated comment for commit eadcde4 with description of existing statuses. It's updated for the latest CI running

✅ Click here to open a full report in a separate page

Successful checks
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
BuildsThere's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS✅ success
ClickBenchRuns [ClickBench](https://github.com/ClickHouse/ClickBench/) with instant-attach table✅ success
Compatibility checkChecks that clickhouse binary runs on distributions with old libc versions. If it fails, ask a maintainer for help✅ success
Docker keeper imageThe check to build and optionally push the mentioned image to docker hub✅ success
Docker server imageThe check to build and optionally push the mentioned image to docker hub✅ success
Docs checkBuilds and tests the documentation✅ 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. Integration 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✅ 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
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

@CurtizJ CurtizJ force-pushed the primary-index-cache branch from e910d18 to ffc4d26 Compare November 20, 2024 17:21
@CurtizJ CurtizJ force-pushed the primary-index-cache branch from ffc4d26 to 7881ae2 Compare November 20, 2024 20:24
@CurtizJ
Copy link
Copy Markdown
Member Author

CurtizJ commented Nov 22, 2024

Fuzzer: #72265.

@CurtizJ CurtizJ marked this pull request as ready for review November 26, 2024 01:23
@alesapin
Copy link
Copy Markdown
Member

0_o

@davenger
Copy link
Copy Markdown
Member

o_O

@alesapin alesapin self-assigned this Nov 26, 2024
Copy link
Copy Markdown
Member

@alesapin alesapin left a comment

Choose a reason for hiding this comment

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

LGTM


IMergeTreeDataPart::IndexPtr IMergeTreeDataPart::loadIndexToCache(PrimaryIndexCache & index_cache) const
{
auto key = PrimaryIndexCache::hash(getDataPartStorage().getFullPath());
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.

Maybe to a comment somewhere, what we use as a key for cache, but it's clear.

@alesapin alesapin added this pull request to the merge queue Nov 26, 2024
Merged via the queue into ClickHouse:master with commit 0d5d424 Nov 26, 2024
@alesapin alesapin deleted the primary-index-cache branch November 26, 2024 12:51
@robot-ch-test-poll4 robot-ch-test-poll4 added the pr-synced-to-cloud The PR is synced to the cloud repo label Nov 26, 2024
baibaichen added a commit to Kyligence/gluten that referenced this pull request Nov 27, 2024
baibaichen added a commit to Kyligence/gluten that referenced this pull request Nov 28, 2024
baibaichen added a commit to Kyligence/gluten that referenced this pull request Nov 28, 2024
baibaichen added a commit to apache/gluten that referenced this pull request Nov 30, 2024
* [GLUTEN-1632][CH]Daily Update Clickhouse Version (20241129)

* Fix Build AND UT Due to [Added cache for primary index](ClickHouse/ClickHouse#72102)

* Fix Build and UT due to [no auto write buffer finalization in destructors](ClickHouse/ClickHouse#68800)

- Make LocalPartitionWriter::evictPartitions called, e.g. set(GlutenConfig.COLUMNAR_CH_SHUFFLE_SPILL_THRESHOLD.key, (1024*1024).toString)

* Fix Build due to [Save several minutes of build time](ClickHouse/ClickHouse#72046)

* Fix Benchmark Build due to [Scatter blocks in hash join without copying](ClickHouse/ClickHouse#67782)

(cherry picked from commit 8d566d6a8b8785e4072ffd6f774eb83b07ac3d8d)

* Fix Benchmark Build

* Fix endless loop due to ClickHouse/ClickHouse#70598

* [Refactor #8100] using CHConf.setCHConfig()

* fix style

---------

Co-authored-by: kyligence-git <[email protected]>
Co-authored-by: Chang Chen <[email protected]>
github-merge-queue bot pushed a commit that referenced this pull request Nov 4, 2025
…e-in-projection-analysis

Fix potential heap-use-after-free in projections analysis after #72102
robot-ch-test-poll1 added a commit that referenced this pull request Nov 4, 2025
Cherry pick #89139 to 25.3: Fix potential heap-use-after-free in projections analysis after #72102
robot-clickhouse added a commit that referenced this pull request Nov 4, 2025
robot-ch-test-poll1 added a commit that referenced this pull request Nov 4, 2025
Cherry pick #89139 to 25.8: Fix potential heap-use-after-free in projections analysis after #72102
robot-clickhouse added a commit that referenced this pull request Nov 4, 2025
robot-ch-test-poll1 added a commit that referenced this pull request Nov 4, 2025
Cherry pick #89139 to 25.9: Fix potential heap-use-after-free in projections analysis after #72102
robot-clickhouse added a commit that referenced this pull request Nov 4, 2025
robot-ch-test-poll1 added a commit that referenced this pull request Nov 4, 2025
Cherry pick #89139 to 25.10: Fix potential heap-use-after-free in projections analysis after #72102
robot-clickhouse added a commit that referenced this pull request Nov 4, 2025
clickhouse-gh bot added a commit that referenced this pull request Nov 4, 2025
Backport #89139 to 25.9: Fix potential heap-use-after-free in projections analysis after #72102
nikitamikhaylov added a commit that referenced this pull request Nov 4, 2025
Backport #89139 to 25.8: Fix potential heap-use-after-free in projections analysis after #72102
nikitamikhaylov added a commit that referenced this pull request Nov 4, 2025
Backport #89139 to 25.10: Fix potential heap-use-after-free in projections analysis after #72102
nikitamikhaylov added a commit that referenced this pull request Nov 5, 2025
Backport #89139 to 25.3: Fix potential heap-use-after-free in projections analysis after #72102
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-feature Pull request with new product feature pr-synced-to-cloud The PR is synced to the cloud repo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Cache for primary index

5 participants