-
Notifications
You must be signed in to change notification settings - Fork 460
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
Set series cache TTL different based on block metadata #7407
Conversation
750e359
to
cc4c0e4
Compare
Instead of using a default TTL of 7d for all index-cache related entries, pick different TTLs based on metadata about the block. This allows entries related to blocks that will be deleted (OOO blocks, 2h, 12h) to expire and be eligible to be evicted sooner than they would otherwise. This change only sets different TTLs for series entries in the cache since they account for most of the space in the cache. Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
cc4c0e4
to
12f13e6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a nit comment, but LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not approving just because I only reviewed BlockTTL()
. I defer to @jhalterman proper review for the rest.
Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! (modulo a last comment)
Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
Like #7407, use different TTL for postings based on block metadata. Use shorter TTLs for cache entries associated with temporary blocks that will be compacted and deleted shortly. Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
Like #7407, use different TTL for postings based on block metadata. Use shorter TTLs for cache entries associated with temporary blocks that will be compacted and deleted shortly. Signed-off-by: Nick Pillitteri <nick.pillitteri@grafana.com>
What this PR does
Instead of using a default TTL of 7d for all index-cache related entries, pick different TTLs based on metadata about the block. This allows entries related to blocks that will be deleted (OOO blocks, 2h, 12h) to expire and be eligible to be evicted sooner than they would otherwise.
This change only sets different TTLs for series entries in the cache since they account for most of the space in the cache.
Which issue(s) this PR fixes or relates to
N/A
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
.about-versioning.md
updated with experimental features.