After upgrading from 2.8.2. to 2.8.3. the piwik_archive_blob tables are growing dramatically (see attached picture).
This already resulted in a corrupt table that had to be repaired with myisamchk.
We had no notable increase in visitors, anyway the table of the current month and january 2014 are growing like hell... I know that in the january table the overall year data is stored. This explains why only current month and january table are affected.
This happended after upgrading from 2.8.2. to 2.8.3. We have the following cronjob running:
30 * * * * piwik /usr/bin/php5 /var/www/webs/piwik/docs/misc/cron/archive.php --url=http://piwik.hirescam.de/ > /dev/null
I think this must be a serious bug - most of the piwik users wont realize this until they run out of disk space or get a corrupt database table...
Regards
Florian
UPDATE: After having a look in the backups I realised that this problem already occured after update from 2.8.1. to 2.8.2. Thus I think it still exists in 2.8.3. as i cant find anything about this issue in the chengelog...
This already resulted in a corrupt table that had to be repaired with myisamchk.
We had no notable increase in visitors, anyway the table of the current month and january 2014 are growing like hell... I know that in the january table the overall year data is stored. This explains why only current month and january table are affected.
This happended after upgrading from 2.8.2. to 2.8.3. We have the following cronjob running:
30 * * * * piwik /usr/bin/php5 /var/www/webs/piwik/docs/misc/cron/archive.php --url=http://piwik.hirescam.de/ > /dev/null
I think this must be a serious bug - most of the piwik users wont realize this until they run out of disk space or get a corrupt database table...
Regards
Florian
UPDATE: After having a look in the backups I realised that this problem already occured after update from 2.8.1. to 2.8.2. Thus I think it still exists in 2.8.3. as i cant find anything about this issue in the chengelog...