-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Compactor: Support --min-time/--max-time filter. #4884
Comments
The request is valid. But configuring min/max time for compaction seems much more complex than setting it for the store gateway. |
After 1:1 with @metonymic-smokey, we think reversing the planning order would work, but it is not as easy as it looks. So it is good to start adding the min/max time filter first. |
Work in progress. |
Signed-off-by: wenmaoba <[email protected]>
Signed-off-by: wenmaoba <[email protected]>
Signed-off-by: wenmaoba <[email protected]>
Signed-off-by: wenmaoba <[email protected]>
Signed-off-by: wenmaoba <[email protected]>
Signed-off-by: wenmaoba <[email protected]>
Signed-off-by: wenmaoba <[email protected]>
Signed-off-by: wenmaoba <[email protected]>
Signed-off-by: wenmaoba <[email protected]> Co-authored-by: wenmaoba <[email protected]>
Addressed by #4909 |
Is your proposal related to a problem?
For my case, the compactor halt or broken for some reason. the compact progress will very be lag.
Then i restart compactor, beacuse the bucket has many blocks, I prefer it could process the more fresh blocks first. but currently, the compactor will start process the oldest block.
Describe the solution you'd like
So, Could we add a time filter like the thanos-store componet does?
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: