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

Store Gateway: index cache with local disk based backend #6241

Open
yeya24 opened this issue Sep 26, 2024 · 0 comments · May be fixed by #6258
Open

Store Gateway: index cache with local disk based backend #6241

yeya24 opened this issue Sep 26, 2024 · 0 comments · May be fixed by #6258

Comments

@yeya24
Copy link
Contributor

yeya24 commented Sep 26, 2024

Is your feature request related to a problem? Please describe.
Store Gateway Index Cache supports 4 backend types: inmemory, memcached, redis and multi level. Multi level is basically a combination of an inmemory cache and a remote cache such as memcached.

Inmemory cache is good for its performance and no additional bandwidth consumption. However, its has small capacity due to memory size.

Remote cache such as memcached are usually distributed and can be seen have much larger capacity. However, querying from remote cache consumes quite a lot of bandwidth.

A middle ground could be a local filesystem/disk based cache backend so that we can achieve a much bigger capacity than the inmemory cache, while keeping better performance and lower bandwidth comsumption than remote cache.

Describe the solution you'd like
Use a disk/filesystem based Storage such as KV store as cache. It should support sized based retention (eviction) strategy to control disk space

Additional context
There is a proposal in Thanos as well thanos-io/thanos#5374

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

Successfully merging a pull request may close this issue.

1 participant