Replies: 1 comment
-
store-gateway typically download headers and blocks from s3. If the number of blocks in block storage is increasing, it's expected pvcs for the store gateways need to be increased too pvcs will increase in size till you have reached the retention configured. Retention is disabled by default (Meaning infinite retention)
Let's say you configure one year retention in the compactor:
With a healthy compactor, there should be one block added per day per tenant, you would need to wait one year till the system stabilizes in terms of number of blocks . Till that happens you will need to increase pvc size or what is probably better: increase the number of store-gateway replicas. Also make sure you have the bucket index enabled for store-gateways as well as the index header lazy enabled Also, make sure the compactor is correctly working and not delayed, as that can cause the number of 2hour blocks to increase also putting pressure in the store-gateways pvcs |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
Store gateway PVCs in our Cortex project are filling up frequently, forcing us to repeatedly increase the size of the PVCs. We are seeking recommendations to resolve this issue.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
We expect the store gateway PVCs to have a more stable and manageable growth rate that does not require constant manual intervention.
Environment:
Infrastructure: Kubernetes
Deployment tool: Pulumi
Issue
Store gateway PVCs are filling up frequently, forcing us to increase their size regularly. We are requesting recommendations to manage or mitigate this issue more effectively.
Beta Was this translation helpful? Give feedback.
All reactions