-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
Trigger compaction to the next level if the data age exceeds periodic_compaction_seconds #12175
Trigger compaction to the next level if the data age exceeds periodic_compaction_seconds #12175
Conversation
a85c469
to
34e7569
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this. We could discuss the approach more, or change it according to the suggestion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just need to keep the compaction behavior for files in last level files same as before, and update release notes.
…_compaction_seconds Currently, the data are always compacted to the same level if exceeds periodic_compaction_seconds which may confuse users, so we change it to allow trigger compaction to the next level here. It's a behavior change to users, it may affect users who have disabled their ttl or ttl > periodic_compaction_seconds.
34e7569
to
3bdd044
Compare
3bdd044
to
0c48c12
Compare
3eeeca7
to
68993e7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
@cbi42 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Currently, the data are always compacted to the same level if exceed periodic_compaction_seconds which may confuse users, so we change it to allow trigger compaction to the next level here. It's a behavior change to users, and may affect users
who have disabled their ttl or ttl > periodic_compaction_seconds.
Relate issue: #12165