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

Monitor disk space usage and prune dataitems when low #211

Open
MRIIOT opened this issue Dec 17, 2022 · 4 comments
Open

Monitor disk space usage and prune dataitems when low #211

MRIIOT opened this issue Dec 17, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@MRIIOT
Copy link
Contributor

MRIIOT commented Dec 17, 2022

I thought retention is already set on db.
What will autoprune do?

@bburns
Copy link
Contributor

bburns commented Dec 17, 2022

retention works, but it's guesswork as to how long you could keep data around - 1w? 1y?

so could have a service prune the db when space gets low.

it would avoid clients using ladder99 and crashing their disks.

not sure how other similar programs handle the issue.

@bburns bburns changed the title Make autoprune service to monitor diskspace and prune dataitems when low. autoprune - make service to monitor diskspace and prune dataitems when low Dec 17, 2022
@tukusejssirs tukusejssirs added the bug Something isn't working label Dec 22, 2022
@tukusejssirs
Copy link
Contributor

@bburns, should this issue be labelled with component:autoprune?

@tukusejssirs tukusejssirs changed the title autoprune - make service to monitor diskspace and prune dataitems when low Monitor disk space usage and prune dataitems when low Dec 22, 2022
@MRIIOT
Copy link
Contributor Author

MRIIOT commented Dec 26, 2022

@tukusejssirs I don't think this is a bug. This is a new feature. The speed of which disk is consumed is all dependent on disk size. Current retention is guesswork, but it works when the guess is correct.

@tukusejssirs
Copy link
Contributor

I don't think this is a bug. This is a new feature. The speed of which disk is consumed is all dependent on disk size. Current retention is guesswork, but it works when the guess is correct.

Well, it depends on the point of view. While I understand your point, IMHO if there is at least one case when the current retention fails (when the guess is incorrect), it should be considered a bug. Yes, this bug is not of a top priority and yes, it does not happen a lot (only rarely). Although it is a bug, as it is of low priority, it does not need to be fixed right away.

YMMV. If you still think it is not a bug, okay, we can change the label to feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants