Hi,
i have an InfluxDB v2 instance with a database (infinite ret. policy).
Some measurements inside are quite big and i do not need infinite data. So i deleted some old data. Then i restarted influxdb. But the size of the data (especially the autogen-folder) is still high.
Any chance to create a query to identify the measurements with highes filesize?
Do you know this problem and how to solve it?
I know that i have to create multiple buckets, but currently i cannot split the data into two or more buckets.
InfluxDB uses a storage engine that periodically compacts data into TSM files. When you delete data, the space isn’t immediately freed up. Instead, InfluxDB marks the data as deleted, and the space is reclaimed during the next compaction cycle.
Is the problem persisting?
I recently performed data deletion across multiple buckets in InfluxDB v2.6.0 to free up server storage, focusing on older and unnecessary data. However, after executing the deletion, I have observed a rapid increase in server size, which is unexpectedly leading to the server reaching its maximum capacity much faster than anticipated.
I would appreciate any insights or recommendations on resolving this issue effectively. Kindly advise on possible reasons for this behavior and potential solutions to mitigate the rapid storage consumption.
Command used : influx delete --bucket ******** --start 2022-03-01T05:30:00Z --stop 2023-04-01T05:15:00Z --org ******* -t ******************************************* -p ‘_measurement=“*******”’
Thanks in advance