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

[v23.3.x] cloud: Add config options to trigger cache trim #19624

Merged

Conversation

jcipar
Copy link
Contributor

@jcipar jcipar commented Jun 11, 2024

Backport of PR #18756

Backports Required

  • none - not a bug fix
  • none - this is a backport
  • none - issue does not exist in previous branches
  • none - papercut/not impactful enough to backport
  • v24.1.x
  • v23.3.x
  • v23.2.x

Release Notes

@jcipar jcipar marked this pull request as ready for review June 11, 2024 17:13
@jcipar jcipar force-pushed the backport-pr-18756-v23.3.x-194 branch from d71c3fd to 9622c8f Compare June 11, 2024 17:53
@piyushredpanda piyushredpanda added this to the v23.3.17 milestone Jun 12, 2024
@jcipar jcipar force-pushed the backport-pr-18756-v23.3.x-194 branch 4 times, most recently from f71f6c5 to 4fd6f7c Compare June 12, 2024 20:03
@@ -35,6 +35,7 @@
#include <algorithm>
Copy link
Member

Choose a reason for hiding this comment

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

[v24.1.x] cloud: Add config options to trigger cache trim

The commit message lists the wrong target version.

Comment on lines 2389 to 2397
, cloud_storage_cache_num_buckets(
*this,
"cloud_storage_cache_num_buckets",
"Divide cloud storage cache across specified number of buckets. This "
"only works for objects with randomized prefixes. The names will not be "
"changed if the value is set to zero.",
{.needs_restart = needs_restart::no, .visibility = visibility::tunable},
0,
{.min = 0, .max = 1024})
Copy link
Member

Choose a reason for hiding this comment

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

I don't see this used in the diff. Is it necessary? If so, please document. Otherwise, can we remove it?

@jcipar jcipar force-pushed the backport-pr-18756-v23.3.x-194 branch from 4fd6f7c to 4b4f69f Compare June 12, 2024 21:44
@piyushredpanda piyushredpanda merged commit dffa703 into redpanda-data:v23.3.x Jun 13, 2024
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants