You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After setting this configuration to 1d and then monitoring it for days after, none of the data is being deleted from the s3 bucket. In the logs there is no mention of "retention" or even "deletion" To Reproduce
Steps to reproduce the behavior:
Set compactor_blocks_retention_period to 1d
Wait a day or more
Expected behavior
I would expect the data older than a day would bd deleted and I would see in the logs that the retention period is being applied.
Environment:
Version: cortex-1.18.1_amd64
Additional Context
In the config file I have
limits:
compactor_blocks_retention_period: 1d
The text was updated successfully, but these errors were encountered:
Hey @adriendinzey, this is not expected. How do you run your compactor? You have to run your compactor in a dedicated service instead of the single binary mode.
The only error I saw in the logs was a failed health check, not sure if that is related. I was previously having issues getting cortex to properly read the compactor_blocks_retention_period, and those errors have since been resolved. Due to that, I believe this indicates the configuration for that flag is being parsed and accepted properly, but the deletion is not occuring.
Describe the bug
After setting this configuration to 1d and then monitoring it for days after, none of the data is being deleted from the s3 bucket. In the logs there is no mention of "retention" or even "deletion"
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect the data older than a day would bd deleted and I would see in the logs that the retention period is being applied.
Environment:
Version: cortex-1.18.1_amd64
Additional Context
In the config file I have
limits:
compactor_blocks_retention_period: 1d
The text was updated successfully, but these errors were encountered: