Hello, I’m running into a very big problem with the size of my Piwik_archive_blob files. I’ve searched around and can’t find a solution that fixes the issue. My server is completely out of disk space because of this and I need help badly.
Hello, we encountered the same problem after updating to Matomo 3.12.0. From 30.10.19 until today our piwik_archive_blob_2019_01.sql.gz grew from 1,5 GB to 27 GB.
We’ve searched around too, but couldn’t find any hint to solve this problem or hints about changing the configuration to stop the daily growth of this file.
I also had this problem several months ago and am having the problem again now. We saw one archive table go from under a GB to over 20GB. It did seem to eventually simply resolve itself but since it seems to cause major spikes in resource usage and is making our backups take up far more space than usual, I’d like to better understand how to prevent and fix it. It does seem to have happened a little bit after we upgraded to 3.12.0. Any help would be appreciated. Thank you!
Thanks all the report. We also would really like to fix this issue.
Can you please try to run the console command: ./console core:purge-old-archive-data all
We ran the suggested command a few times and it reduced the size of the two largest archive blobs by about 10% but unfortunately this means they are still collectively taking up about 27GB. Possibly coincidentally our largest blob is also piwik_archive_blob_2019_01 at ~25GB
Our server went down because this bug ate up available space.
Does the update also cleans up the faulty data from from the 2019-01 tables?
How can this be properly cleaned?
updated to 3.13.0 last week and looks like everything is working fine. Database size reduced from 35GB to ~7GB. Archiving is now back to speedy and less resource intensive. Thank you for the help!