tickets #132365
closedmetrics.o.o: disk space running low
0%
Description
The disk space for storing cached files for aggregated access metrics is running low.
/dev/vdb1 30G 28G 829M 98% /space
Please expand the volume.
Updated by crameleon over 1 year ago
- Category set to Servers hosted in NBG
- Status changed from New to Rejected
I can increase the disk space, but I do not think a user needs more than 20GB of caches.
# du -h -d 1 /space/home/osrt-metrics/.cache/openSUSE-release-tools/metrics-access/
624K /space/home/osrt-metrics/.cache/openSUSE-release-tools/metrics-access/vendor
12K /space/home/osrt-metrics/.cache/openSUSE-release-tools/metrics-access/copy
19G /space/home/osrt-metrics/.cache/openSUSE-release-tools/metrics-access/ipv4
2.0G /space/home/osrt-metrics/.cache/openSUSE-release-tools/metrics-access/ipv6
21G /space/home/osrt-metrics/.cache/openSUSE-release-tools/metrics-access/
Some of the .json files in these directories seem to be over ten years old:
# find /space/home/osrt-metrics/.cache/openSUSE-release-tools/metrics-access/ -name '*.json' -type f|grep -Po '20\d\d'|sort -u
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
Please do some cleaning up and re-open this ticket should you still require more disk space.
Updated by witekbedyk over 1 year ago
These JSON files in .cache directory are not really cache files. They consist intermediary data parsed from access logs to aggregate the numbers exposed at metrics.o.o. The parsing step is relatively time consuming. I think it is good to keep that data somewhere. The idea here is to be able to modify the aggregation procedure without repeating the parsing step.
Having said that, I think we could move the older files somewhere (e.g. backup.o.o.) but we should not just delete them.
Updated by crameleon over 1 year ago
- Status changed from Rejected to Resolved
Thanks for elaborating - I see, it would probably be good to store them in a more appropriate location in this case - because I can definitely see another administrator deleting old stuff in "cache" directories to free up disk space.
I followed your request and set the disk size to 60GB.
Updated by cboltz over 1 year ago
Just wondering - what about compressing the older json files?