I appear to be having the same problem. I tried running the “SELECT idsite, date1, date2, period, name, COUNT(*) as count FROM piwik_archive_numeric_2015_01 GROUP BY idsite, date1, date2, period, name HAVING count > 1;” query and got over a hundred rows with ‘count’ higher than 2, at least 6 with ‘count’ of 42. Here’s a screenshot of part of that, sorted by highest ‘count’:
[attachment 2141 Highdbcount.png]
We upgraded our 1.7.1 Piwik to 2.8.3 in the first week of January 2015, and then to 2.10.0 this past weekend. The visits we’re tracking have been consistent, but the piwik_archive_blob_2015_01 and piwik_archive_blob_2015_02 (which has barely started) are already triple the size of December 2014 (1,594,160 Rows for January vs 517,402 Rows for December). The piwik_numeric_2015_01 and 02 are similarly oversized (516,465 Rows for January vs 214,879 Rows for December 2014). We’re using MySQL 5.6
I tried running the “php C:/inetpub/[our piwik folder]/console core:run-scheduled-tasks --force” command as recommended above, but didn’t see any effect at all on the database size. I’ve attached a screenshot of the command results. Of particuarly concern is about 115 lines of “Purging temporary archives: skipped”. What might be causing the skipped purging? Is there something I can do directly through MySQL in the meantime (the db is now about 9Gb/50% larger than it should be).
[attachment 2139 ForcedScheduledTasks.png]
Also, are these [Deletelogs] configurations relevant?
delete_logs_enable = 1
delete_logs_schedule_lowest_interval = 1
delete_logs_older_than = 120
delete_max_rows_per_run = 500
Any advice would be appreciated, Thank you.