Skip to content
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

Cache HEAD API requests to object storage in the plain_rewritable disk #70915

Merged
merged 7 commits into from
Oct 25, 2024

Conversation

jkartseva
Copy link
Contributor

@jkartseva jkartseva commented Oct 22, 2024

  • Cache last modified metadata object in addition to file size.
  • Use metadata object cache to determine if a file exists.
  • Evict from cache when metadata is unlinked.

Changelog category (leave one):

  • Improvement

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

Reduce the number of object storage HEAD API requests in the plain_rewritable disk.

Documentation entry for user-facing changes

  • Documentation is written (mandatory for new features)

Information about CI checks: https://clickhouse.com/docs/en/development/continuous-integration/

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

@jkartseva jkartseva added the can be tested Allows running workflows for external contributors label Oct 22, 2024
@jkartseva jkartseva marked this pull request as draft October 22, 2024 09:26
@robot-ch-test-poll2 robot-ch-test-poll2 added the pr-improvement Pull request with some product improvements label Oct 22, 2024
@robot-clickhouse-ci-1
Copy link
Contributor

robot-clickhouse-ci-1 commented Oct 22, 2024

This is an automated comment for commit 91d7b7b 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

@kssenii kssenii self-assigned this Oct 22, 2024
@jkartseva jkartseva force-pushed the reduce-api-calls-cost branch 2 times, most recently from c8f2f6e to c8685b1 Compare October 23, 2024 00:21
@jkartseva jkartseva changed the title Cache HEAD API requests to object_storage in the plain_rewritable disk Cache HEAD API requests to object storage in the plain_rewritable disk Oct 23, 2024
@jkartseva jkartseva force-pushed the reduce-api-calls-cost branch 5 times, most recently from 2c27c2e to a2859a1 Compare October 23, 2024 05:56
@jkartseva jkartseva marked this pull request as ready for review October 23, 2024 05:57
- Cache last modified metadata object in addition to file size.
- Use metadata object cache to determine if a file exists.
- Evict from cache when metadata is unlinked.
@jkartseva jkartseva force-pushed the reduce-api-calls-cost branch from a2859a1 to 2f533cb Compare October 24, 2024 03:46
@jkartseva jkartseva force-pushed the reduce-api-calls-cost branch from 2f533cb to 2e38791 Compare October 24, 2024 03:50
@@ -13,21 +13,28 @@ class MetadataStorageFromPlainRewritableObjectStorage final : public MetadataSto
{
private:
const std::string metadata_key_prefix;
std::shared_ptr<InMemoryPathMap> path_map;
std::shared_ptr<InMemoryDirectoryPathMap> path_map;
Copy link
Member

Choose a reason for hiding this comment

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

I'd rename path_map as well, to something like directory_path_map, or directory_to_remote_info_map, or something else...

auto object_key = object_storage->generateObjectKeyForPath(path, std::nullopt /* key_prefix */);
if (auto metadata = object_storage->tryGetObjectMetadata(object_key.serialize()))
return std::make_shared<ObjectMetadataEntry>(metadata->size_bytes, metadata->last_modified.epochTime());
return nullptr;
Copy link
Member

Choose a reason for hiding this comment

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

If we once failed to get object metadata, for example, because s3 was temporarily unavailable, then looks like we will add nullptr to cache for this path and it would always be nullptr and never updated, should we instead check the error code because of which we failed to get metadata, and if it is key_doesnt_exist, then probably ok to leave nullptr in cache, but for another reason seems better not to cache it?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed so null pointer is not cached.
I think storing a nullptr for non-existed key would be wrong in the present implementation, since I don't update the cache when a file is written.

@jkartseva jkartseva added this pull request to the merge queue Oct 24, 2024
Merged via the queue into ClickHouse:master with commit 2e61f2b Oct 25, 2024
211 checks passed
@jkartseva jkartseva deleted the reduce-api-calls-cost branch October 25, 2024 00:27
@robot-ch-test-poll3 robot-ch-test-poll3 added the pr-synced-to-cloud The PR is synced to the cloud repo label Oct 25, 2024
@robot-ch-test-poll3 robot-ch-test-poll3 added the pr-backports-created Backport PRs are successfully created, it won't be processed by CI script anymore label Oct 29, 2024
@jkartseva jkartseva added v24.9-must-backport v24.8-must-backport pr-must-backport Pull request should be backported intentionally. Use this label with great care! and removed pr-backports-created Backport PRs are successfully created, it won't be processed by CI script anymore pr-backports-created-cloud labels Oct 30, 2024
jkartseva added a commit that referenced this pull request Oct 31, 2024
…89e457b9669b7a9e9084987ca144b

Cherry pick #70915 to 24.8: Cache HEAD API requests to object storage in the plain_rewritable disk
robot-clickhouse added a commit that referenced this pull request Oct 31, 2024
jkartseva added a commit that referenced this pull request Oct 31, 2024
…89e457b9669b7a9e9084987ca144b

Cherry pick #70915 to 24.9: Cache HEAD API requests to object storage in the plain_rewritable disk
robot-clickhouse added a commit that referenced this pull request Oct 31, 2024
@robot-ch-test-poll3 robot-ch-test-poll3 added the pr-backports-created Backport PRs are successfully created, it won't be processed by CI script anymore label Oct 31, 2024
jkartseva pushed a commit that referenced this pull request Oct 31, 2024
jkartseva pushed a commit that referenced this pull request Oct 31, 2024
robot-ch-test-poll3 added a commit that referenced this pull request Oct 31, 2024
Backport #70915 to 24.8: Cache HEAD API requests to object storage in the plain_rewritable disk
robot-ch-test-poll added a commit that referenced this pull request Dec 4, 2024
Backport #70915 to 24.9: Cache HEAD API requests to object storage in the plain_rewritable disk
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
can be tested Allows running workflows for external contributors pr-backports-created Backport PRs are successfully created, it won't be processed by CI script anymore pr-backports-created-cloud pr-improvement Pull request with some product improvements pr-must-backport Pull request should be backported intentionally. Use this label with great care! pr-synced-to-cloud The PR is synced to the cloud repo v24.8-must-backport v24.9-must-backport v24.10-must-backport
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants