Cache meta iteration in store-gateway
Open
v1
- Dominant language
- Go
- Stars
- 11.7k
- Forks
- 802
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 80
Description
Right now each store-gateway download the last 31d metadata blocks on initial startup, on ring change (new member), and periodically (default 15m).
This can causes high CPU usage by store-gateways since there's can be many blocks (thousand).
I think we can improve this, by only updating the latest block prefixes and caching meta files on disk/memory.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.