[Bug] Serialization failure: 1213 Deadlock found when marking archives as invalid

[tsteur]

What happened?

Since Matomo 5 we're seeing 3-6 times per day below fatal errors. We're currently on 5.0.0-rc9. This did not happen in Matomo 4 or only very rarely. There must have been some change.

Stack trace 1

Error: {"message":"SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction","file":"/libs/Zend/Db/Statement/Pdo.php","line":236,"backtrace":" on /libs/Zend/Db/Statement/Pdo.php(236)\n#0 /libs/Zend/Db/Statement.php(300): Zend_Db_Statement_Pdo->execute(Array)\n#1 /libs/Zend/Db/Adapter/Abstract.php(479): Zend_Db_Statement->execute(Array)\n#2 /libs/Zend/Db/Adapter/Pdo/Abstract.php(238): Zend_Db_Adapter_Abstract->query('UPDATE archive...', Array)\n#3 /core/Db/Adapter/Pdo/Mysql.php(332): Zend_Db_Adapter_Pdo_Abstract->query('UPDATE archive_...', Array)\n#4 /core/Db.php(281): Piwik\Db\Adapter\Pdo\Mysql->query('UPDATE archive_...', Array)\n#5 /core/DataAccess/Model.php(340): Piwik\Db::query('UPDATE archive_...', Array)\n#6 /core/Archive/ArchiveInvalidator.php(701): Piwik\DataAccess\Model->updateRangeArchiveAsInvalidated('archive_numeric...', Array, Array, Object(Piwik\Segment))\n#7 /core/Archive/ArchiveInvalidator.php(328): Piwik\Archive\ArchiveInvalidator->markArchivesInvalidated(Array, Array, Object(Piwik\Segment), true, false, NULL)\n#8 /plugins/CoreAdminHome/API.php(175): Piwik\Archive\ArchiveInvalidator->markArchivesAsInvalidated(Array, Array, 'day', Object(Piwik\Segment), false, false)\n#9 /core/CronArchive.php(982): Piwik\Plugins\CoreAdminHome\API->invalidateArchivedReports(Array, Array, 'day', Object(Piwik\Segment), false, false)\n#10 /core/CronArchive.php(908): Piwik\CronArchive->invalidateWithSegments(Array, '2023-12-31', 'day', false, false)\n#11 /core/CronArchive.php(858): Piwik\CronArchive->invalidateRecentDate('today', '12')\n#12 /core/CronArchive.php(812): Piwik\CronArchive->invalidateArchivedReportsForSitesThatNeedToBeArchivedAgainImpl('12')\n#13 /core/Tracker/Cache.php(296): Piwik\CronArchive->Piwik\{closure}()\n#14 /core/CronArchive.php(813): Piwik\Tracker\Cache::withDelegatedCacheClears(Object(Closure))\n#15 /core/CronArchive/QueueConsumer.php(178): Piwik\CronArchive->invalidateArchivedReportsForSitesThatNeedToBeArchivedAgain('12')\n#16 /core/CronArchive.php(390): Piwik\CronArchive\QueueConsumer->getNextArchivesToProcess()\n#17 /core/CronArchive.php(276): Piwik\CronArchive->run()\n#18 /core/Access.php(661): Piwik\CronArchive->Piwik\{closure}()\n#19 /core/CronArchive.php(282): Piwik\Access::doAsSuperUser(Object(Closure))\n#20 /plugins/CoreConsole/Commands/CoreArchiver.php(32): Piwik\CronArchive->main()\n#21 /core/Plugin/ConsoleCommand.php(110): Piwik\Plugins\CoreConsole\Commands\CoreArchiver->doExecute()\n#22 /vendor/symfony/console/Command/Command.php(298): Piwik\Plugin\ConsoleCommand->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))\n#23 /core/Plugin/ConsoleCommand.php(125): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))\n#24 /vendor/symfony/console/Application.php(1040): Piwik\Plugin\ConsoleCommand->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))\n#25 /vendor/symfony/console/Application.php(301): Symfony\Component\Console\Application->doRunCommand(Object(Piwik\Plugins\CoreConsole\Commands\CoreArchiver), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))\n#26 /core/Console.php(106): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))\n#27 [internal function]: Piwik\Console->originDoRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))\n#28 /core/Console.php(145): call_user_func(Array, Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))\n#29 /core/Access.php(670): Piwik\Console->Piwik\{closure}()\n#30 /core/Console.php(146): Piwik\Access::doAsSuperUser(Object(Closure))\n#31 /core/Console.php(85): Piwik\Console->doRunImpl(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))\n#32 /vendor/symfony/console/Application.php(171): Piwik\Console->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))\n#33 /console(32): Symfony\Component\Console\Application->run()\n#34 {main}\ncaused by: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction on /libs/Zend/Db/Statement/Pdo.php(233)\n#0 /libs/Zend/Db/Statement/Pdo.php(233): PDOStatement->execute()\n#1 /libs/Zend/Db/Statement.php(300): Zend_Db_Statement_Pdo->execute(Array)\n#2 /libs/Zend/Db/Adapter/Abstract.php(479): Zend_Db_Statement->execute(Array)\n#3 /libs/Zend/Db/Adapter/Pdo/Abstract.php(238): Zend_Db_Adapter_Abstract->query('UPDATE archive...', Array)\n#4 /core/Db/Adapter/Pdo/Mysql.php(332): Zend_Db_Adapter_Pdo_Abstract->query('UPDATE archive_...', Array)\n#5 /core/Db.php(281): Piwik\Db\Adapter\Pdo\Mysql->query('UPDATE archive_...', Array)\n#6 /core/DataAccess/Model.php(340): Piwik\Db::query('UPDATE archive_...', Array)\n#7 /core/Archive/ArchiveInvalidator.php(701): Piwik\DataAccess\Model->updateRangeArchiveAsInvalidated('archive_numeric...', Array, Array, Object(Piwik\Segment))\n#8 /core/Archive/ArchiveInvalidator.php(328): Piwik\Archive\ArchiveInvalidator->markArchivesInvalidated(Array, Array, Object(Piwik\Segment), true, false, NULL)\n#9 /plugins/CoreAdminHome/API.php(175): Piwik\Archive\ArchiveInvalidator->markArchivesAsInvalidated(Array, Array, 'day', Object(Piwik\Segment), false, false)\n#10 /core/CronArchive.php(982): Piwik\Plugins\CoreAdminHome\API->invalidateArchivedReports(Array, Array, 'day', Object(Piwik\Segment), false, false)\n#11 /core/CronArchive.php(908): Piwik\CronArchive->invalidateWithSegments(Array, '2023-12-31', 'day', false, false)\n#12 /core/CronArchive.php(858): Piwik\CronArchive->invalidateRecentDate('today', '12')\n#13 /core/CronArchive.php(812): Piwik\CronArchive->invalidateArchivedReportsForSitesThatNeedToBeArchivedAgainImpl('12')\n#14 /core/Tracker/Cache.php(296): Piwik\CronArchive->Piwik\{closure}()\n#15 /core/CronArchive.php(813): Piwik\Tracker\Cache::withDelegatedCacheClears(Object(Closure))\n#16 /core/CronArchive/QueueConsumer.php(178): Piwik\CronArchive->invalidateArchivedReportsForSitesThatNeedToBeArchivedAgain('12')\n#17 /core/CronArchive.php(390): Piwik\CronArchive\QueueConsumer->getNextArchivesToProcess()\n#18 /core/CronArchive.php(276): Piwik\CronArchive->run()\n#19 /core/Access.php(661): Piwik\CronArchive->Piwik\{closure}()\n#20 /core/CronArchive.php(282): Piwik\Access::doAsSuperUser(Object(Closure))\n#21 /plugins/CoreConsole/Commands/CoreArchiver.php(32): Piwik\CronArchive->main()\n#22 /core/Plugin/ConsoleCommand.php(110): Piwik\Plugins\CoreConsole\Commands\CoreArchiver->doExecute()\n#23 /vendor/symfony/console/Command/Command.php(298): Piwik\Plugin\ConsoleComman

Stack trace 2

[2023-12-31 01:58:08] piwik.ERROR: Scheduler: Error SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction for task 'Piwik\Plugins\CoreAdminHome\Tasks.purgeInvalidatedArchives' {"errorMessage":"SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction","task":"Piwik\Plugins\CoreAdminHome\Tasks.purgeInvalidatedArchives"} {"class":"CoreAdminHome","request_id":"29337"}

What should happen?

No fatal error

How can this be reproduced?

Unsure.

Executed command for stack trace 1 was:

SERVER ARGV: ["/var/www/html/console", "core:archive","--disable-scheduled-tasks","--force-idsites=12","--force-periods=week,month,year","--force-date-range=2023-01-01,2023-01-01"]

Which seems to be triggered by GA Importer. Unsure if there was maybe any change in GA importer that this is being triggered more often? I don't know why GA Importer executes this command.

Executed command for stack trace 2 was:

console core:archive --concurrent-requests-per-website=1 --skip-segments-today --concurrent-archivers=4 --no-ansi

Matomo version

5.0

PHP version

No response

Server operating system

No response

What browsers are you seeing the problem on?

No response

Computer operating system

No response

Relevant log output

No response

Validations

• Read our Contributing Guidelines.
• Follow our Security Policy.
• Check that there isn't already an issue that reports the same bug to avoid creating duplicates.
• The provided steps to reproduce is a minimal reproducible of the Bug.

[sgiehl]

I guess this one might be very hard to reproduce. Looking through the code it seems the GA Importer plugin always did trigger a core:archive after importing data, but I don't know if something was changed or if this might bet triggered more often now.

Looking at the stack trace (1) it seems the exception is thrown while marking some archives as invalidated. Maybe this is some sort of race condition when the GA Importer triggers the archiving while a normal archiving process is already running or similar.

[MatomoForumNotifications]

This issue has been mentioned on Matomo forums. There might be relevant details there:

https://forum.matomo.org/t/core-archive-has-serialization-failure-1213-deadlock-when-running-with-more-than-concurrent-archivers-1/58414/2

[Schwuuuuup]

Hi, yes that forum post is mine.

I'll quickly paste it over to here, and happily answer any questions about it.

Hi,
I’m not sure if this is a bug or a performance issue so here are our specs:

Matomo installation

• over a 1000 sites (most of them tiny)
• DB size ~42GB.
• Matomo in Docker containers (one for PHP-FPM one for the webserver)
• MariaDB 10.6 on same machine connected via local socket

Our Machine:

• 8 CPU cores (VMWare Guest)
• 20GB RAM. (16GB RAM was a bit tight with Matomo 4.x, so we gave 5.1 20GB)

Since migrating to the new machine and upgrading to Matomo 5.0 (later 5.1) we get the error message below several times a day. Our cron job runs every 15 minutes, but is usually restricted to --concurrent-archivers 8. In the past we had no problems but now we get these deadlocks even with a maximum of 2 concurrent archivers.

ERROR     [2024-07-01 02:38:55] 1418677  Uncaught exception: /var/www/html/libs/Zend/Db/Statement/Pdo.php(236): SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction [Query: , CLI mode: 1]
 
In Pdo.php line 236:
                                                                               
  SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to   
  get lock; try restarting transaction                                         
                                                                               
 
In Pdo.php line 233:
                                                                               
  SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to   
  get lock; try restarting transaction                                         
                                                                               
 
core:archive [--url URL] [--skip-idsites [SKIP-IDSITES]] [--skip-all-segments] [--force-idsites [FORCE-IDSITES]] [--skip-segments-today] [--force-periods [FORCE-PERIODS]] [--force-date-last-n [FORCE-DATE-LAST-N]] [--force-date-range [FORCE-DATE-RANGE]] [--force-idsegments FORCE-IDSEGMENTS] [--concurrent-requests-per-website [CONCURRENT-REQUESTS-PER-WEBSITE]] [--concurrent-archivers [CONCURRENT-ARCHIVERS]] [--max-websites-to-process MAX-WEBSITES-TO-PROCESS] [--max-archives-to-process MAX-ARCHIVES-TO-PROCESS] [--disable-scheduled-tasks] [--accept-invalid-ssl-certificate] [--php-cli-options [PHP-CLI-OPTIONS]] [--force-all-websites] [--force-report [FORCE-REPORT]]

We migrated the VM to faster hardware. We migrated the database to SSD-based storrage. We upped the Caching of MariaDB… but now we are running out of ideas, what else we could try.
One single archiver seems to be not fast enough to keep up with the incoming data, so we relied on the cron starting additional jobs utilizing more CPU cores when they were needed.

Any Ideas what goes wrong?

Best
TOM

[Schwuuuuup]

Anything new in this regard? We are still on 2-4 failed cron jobs per day.
I can try to provide additional data, if you tell me what to look for

[MichaelRoosz]

Same in my setup, happens around 20 times a day since we upgraded from Matomo 4 to Matomo 5.

We do not use GA Importer.
We have around 400 sites, database is around 5 TB.

I will try to investigate more.

Update:
all of the deadlocks happened for table piwik_archive_numeric_2024_10, so for sure an issue with archiving

Update 2:
The deadlocks happen most of the time (90%, 11 out of 12 times in one log file), for these two types of queries:

UPDATE piwik_archive_numeric_2024_10 SET value = 4 WHERE name LIKE 'done4b5fe38507a9926a0847aa5664450f7d%'
                   AND idsite IN (261)
                   AND ((period = 5 AND ((date1 <= '2024-10-31 00:00:00' AND '2024-10-31 00:00:00' <= date2))) OR (period = 5 AND ((date1 <= '2024-10-28 00:00:00' AND '2024-11-03 00:00:00' <= date2))) OR (period = 5 AND ((date1 <= '2024-10-01 00:00:00' AND '2024-10-31 00:00:00' <= date2))))

VS

UPDATE `piwik_archive_numeric_2024_10` SET `value` = 4 WHERE idarchive IN (3889425,3889382) AND name LIKE 'done03a5905ad8ca31c6c19723b6ff9ed99d%'

[samjf]

Agreed with Michael and Schwup. From my experience this can be solidly reproduced in a high concurrency environment.

[chopsol]

Since the update to version 5.2.0 I also receive the message.
I was able to limit it to this segment: deviceType==smartphone,deviceType==phablet
All other segments did not have this problem.

EDIT: Unfortunately, I have to correct myself. Now this error message also came to other segments.

Here are the two lines from the archiving.

ERROR [2024-12-14 15:14:55] 953457 Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=7&period=day&date=2024-12-03&format=json&segment=deviceType%3D%3Dsmartphone%2CdeviceType%3D%3Dphablet&trigger=archivephp. Response was '{"result":"error","message":"SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction - in plugin Goals. #0 \/core\/ArchiveProcessor\/Loader.php(317): Piwik\\ArchiveProcessor\\PluginsArchiver->callAggregateAllPlugins() #1 \/core\/ArchiveProcessor\/Loader.php(186): Piwik\\ArchiveProcessor\\Loader->prepareAllPluginsArchive() #2 \/core\/ArchiveProcessor\/Loader.php(165): Piwik\\ArchiveProcessor\\Loader->insertArchiveData() #3 \/core\/ArchiveProcessor\/Loader.php(105): Piwik\\ArchiveProcessor\\Loader->prepareArchiveImpl() #4 \/core\/Context.php(76): Piwik\\ArchiveProcessor\\Loader->Piwik\\ArchiveProcessor\\{closure}() #5 \/core\/ArchiveProcessor\/Loader.php(102): Piwik\\Context::changeIdSite() #6 \/plugins\/CoreAdminHome\/API.php(306): Piwik\\ArchiveProcessor\\Loader->prepareArchive() #7 [internal function]: Piwik\\Plugins\\CoreAdminHome\\API->archiveReports() #8 \/core\/API\/Proxy.php(256): call_user_func_array() #9 \/core\/Context.php(29): Piwik\\API\\Proxy->Piwik\\API\\{closure}() #10 \/core\/API\/Proxy.php(159): Piwik\\Context::executeWithQueryParameters() #11 \/core\/API\/Request.php(274): Piwik\\API\\Proxy->call() #12 \/plugins\/API\/Controller.php(46): Piwik\\API\\Request->process() #13 [internal function]: Piwik\\Plugins\\API\\Controller->index() #14 \/core\/FrontController.php(645): call_user_func_array() #15 \/core\/FrontController.php(169): Piwik\\FrontController->doDispatch() #16 \/core\/dispatch.php(33): Piwik\\FrontController->dispatch() #17 \/index.php(25): require_once('...') #18 \/core\/CliMulti\/RequestCommand.php(76): require_once('...') #19 \/core\/Plugin\/ConsoleCommand.php(138): Piwik\\CliMulti\\RequestCommand->doExecute() #20 \/vendor\/symfony\/console\/Command\/Command.php(298): Piwik\\Plugin\\ConsoleCommand->execute() #21 \/core\/Plugin\/ConsoleCommand.php(153): Symfony\\Component\\Console\\Command\\Command->run() #22 \/vendor\/symfony\/console\/Application.php(1040): Piwik\\Plugin\\ConsoleCommand->run() #23 \/vendor\/symfony\/console\/Application.php(301): Symfony\\Component\\Console\\Application->doRunCommand() #24 \/core\/Console.php(113): Symfony\\Component\\Console\\Application->doRun() #25 [internal function]: Piwik\\Console->originDoRun() #26 \/core\/Console.php(152): call_user_func() #27 \/core\/Access.php(672): Piwik\\Console->Piwik\\{closure}() #28 \/core\/Console.php(150): Piwik\\Access::doAsSuperUser() #29 \/core\/Console.php(92): Piwik\\Console->doRunImpl() #30 \/vendor\/symfony\/console\/Application.php(171): Piwik\\Console->doRun() #31 \/console(32): Symfony\\Component\\Console\\Application->run() #32 {main}, caused by: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction #0 \/libs\/Zend\/Db\/Statement.php(300): Zend_Db_Statement_Pdo->_execute() #1 \/libs\/Zend\/Db\/Adapter\/Abstract.php(479): Zend_Db_Statement->execute() #2 \/libs\/Zend\/Db\/Adapter\/Pdo\/Abstract.php(238): Zend_Db_Adapter_Abstract->query() #3 \/core\/Db\/Adapter\/Pdo\/Mysql.php(334): Zend_Db_Adapter_Pdo_Abstract->query() #4 \/core\/Db.php(286): Piwik\\Db\\Adapter\\Pdo\\Mysql->query() #5 \/core\/DataAccess\/Model.php(361): Piwik\\Db::query() #6 \/core\/Archive\/ArchiveInvalidator.php(734): Piwik\\DataAccess\\Model->updateRangeArchiveAsInvalidated() #7 \/core\/Archive\/ArchiveInvalidator.php(334): Piwik\\Archive\\ArchiveInvalidator->markArchivesInvalidated() #8 \/core\/ArchiveProcessor.php(788): Piwik\\Archive\\ArchiveInvalidator->markArchivesAsInvalidated() #9 \/core\/Plugin\/Archiver.php(411): Piwik\\ArchiveProcessor->processDependentArchive() #10 \/core\/Plugin\/Archiver.php(231): Piwik\\Plugin\\Archiver->processDependentArchivesForPlugins() #11 \/core\/ArchiveProcessor\/PluginsArchiver.php(186): Piwik\\Plugin\\Archiver->callAggregateDayReport() #12 /core\/ArchiveProcessor\/Loader.php(317): Piwik ... \/console(32): Symfony\\Component\\Console\\Application->run()\n#45 {main}"}' INFO [2024-12-14 15:14:55] 953457 Skipped Archiving website id 1, period = day, date = 2024-12-03, segment = 'deviceType==smartphone,deviceType==phablet', 0 visits found. Time elapsed: 0.532s

[Nissulya]

Since yesterday we’ve got the same problem. We’ve got errors like:

Error: Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=147&period=month&date=2024-12-01&format=json&segment=pageUrl%3D%5Ehttps%25253A%25252F%25252Fwww.xyz.de%25252F2-handlungsfelder%25252F02-nachhaltigkeitsberichterstattung.html&trigger=archivephp. Response was '{"result":"error","message":"SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; when running the piwik-archive cron-job. This doesn't always affect the same segments

Our setting is:
Ubuntu 22.04.5 LTS
Matomo: 5.2.0
MariaDB: 10.6.18-MariaDB-0ubuntu0.22.04.1
PHP versions tested: from 8.1 to 8.3.14
213 web sites
227 segments
Piwik-DB: 109 GB

[Nissulya]

We now log the locks in the mysql-error log file, this is an example:

2024-12-19 10:27:46 266487 [Note] InnoDB: Transactions deadlock detected, dumping detailed information.
2024-12-19 10:27:46 266487 [Note] InnoDB:
*** (1) TRANSACTION:

TRANSACTION 1223074156, ACTIVE 0 sec fetching rows
mysql tables in use 1, locked 1
LOCK WAIT 36 lock struct(s), heap size 8312, 4011 row lock(s)
MariaDB thread id 266487, OS thread handle 140120226780736, query id 8852312 localhost piwik Updating
UPDATE piwik_archive_numeric_2024_12 SET value = 4 WHERE name LIKE 'done8fc254e4e4251c98d685fc79f2ec1dd1%'
                   AND idsite IN (138)
                   AND ((period = 5 AND ((date1 <= '2024-12-19 00:00:00' AND '2024-12-19 00:00:00' <= date2))) OR (period = 5 AND ((date1 <= '2024-12-16 00:00:00' AND '2024-12-22 00:00:00' <= date2))) OR (period = 5 AND ((date1 <= '2024-12-01 00:00:00' AND '2024-12-31 00:00:00' <= date2))))
2024-12-19 10:27:46 266487 [Note] InnoDB: *** WAITING FOR THIS LOCK TO BE GRANTED:

RECORD LOCKS space id 422 page no 1521 n bits 216 index PRIMARY of table `piwik`.`piwik_archive_numeric_2024_12` trx id 1223074156 lock_mode X locks rec but not gap waiting
Record lock, heap no 39 PHYSICAL RECORD: n_fields 10; compact format; info bits 0
 0: len 4; hex 00075293; asc   R ;;
 1: len 12; hex 626f756e63655f636f756e74; asc bounce_count;;
 2: len 6; hex 000000000000; asc       ;;
 3: len 7; hex 80000000000000; asc        ;;
 4: len 4; hex 0000008a; asc     ;;
 5: len 3; hex 8fd18c; asc    ;;
 6: len 3; hex 8fd192; asc    ;;
 7: len 1; hex 05; asc  ;;
 8: len 5; hex 99b5267639; asc   &v9;;
 9: len 8; hex 0000000000d08540; asc        @;;

2024-12-19 10:27:46 266487 [Note] InnoDB: *** CONFLICTING WITH:

RECORD LOCKS space id 422 page no 1521 n bits 216 index PRIMARY of table `piwik`.`piwik_archive_numeric_2024_12` trx id 1223074158 lock_mode X