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
@gebn This is one new feature in the latest release #4801.
The compactor now will synchronize blocks metadata every 5m to calculate the progress of compaction, downsampling and retention and expose the progress to metrics.
To change this behavior, you can modify the --compact.progress-interval flag to a larger time or use 0s to disable progress checking if you don't worry about your compaction progress.
@yeya24 Ah, thanks for the prompt reply! I did look over the changelog, but interpreted that entry as only exposing additional metrics rather than adding a new feature.
Thanos, Prometheus and Golang version used:
Object Storage Provider: AWS S3
What happened:
Since upgrading from v0.23.1 to v0.24.0, without changing any params or config, Compact synchronises block metadata every 5 minutes.
What you expected to happen:
Given the config below, Compact to only synchronise every 8 hours, with no requests to S3 in between, as before.
How to reproduce it (as minimally and precisely as possible):
Full logs to relevant components:
Logs showing block sync running every 5 mins:
S3 operations by Compact in the last week (upgrade @ 6pm on 2021-12-22):
The text was updated successfully, but these errors were encountered: