Skip to content
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: Make debug.max-compaction-level Public #4283

Closed
Jakob3xD opened this issue May 28, 2021 · 2 comments
Closed

Compactor: Make debug.max-compaction-level Public #4283

Jakob3xD opened this issue May 28, 2021 · 2 comments
Labels

Comments

@Jakob3xD
Copy link
Contributor

Jakob3xD commented May 28, 2021

Is your proposal related to a problem?

One of my minio servers has a compactor running with a retention set to 30 Days for all resolution.
Currently the compactor creates blocks with a duration of 14 days. This can leads to an storage issue as only every two weeks blocks get removed by moving out of the retention time frame. More over the downsampler creates high storage peaks while creating the 5m and 1h blocks out of the 14d raw block.

Describe the solution you'd like

My wish is to make the hidden flag debug.max-compaction-level a public one with a small documentation entry with why this can be set and the downsides if there are some.

Additional context

Description of the following graph:
It displays the last 8 weeks.
The high peaks are created by the downsampler creating the blocks of 5m and 1h retention out of the raw 14d blocks and deleting the old 2d blocks. In two weeks the storage increase by ~3TB and drops by the end for around 2.9TB. Limiting the duration to 2d will increase the block drop ration and resulting in a more flatted graph and a better storage usage.
grafik

@Jakob3xD
Copy link
Contributor Author

There is already a hidden flag for my request. Setting debug.max-compaction-level to 3 will end at 2d blocks.

@Jakob3xD Jakob3xD changed the title Compactor: Limit Block Duration Compactor: Make debug.max-compaction-level Public Jun 11, 2021
@stale
Copy link

stale bot commented Aug 13, 2021

Hello 👋 Looks like there was no activity on this issue for the last two months.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity in the next two weeks, this issue will be closed (we can always reopen an issue if we need!). Alternatively, use remind command if you wish to be reminded at some point in future.

@stale stale bot added the stale label Aug 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant