2019 Report
PHP Warning: [data-update-failed]: A data update callback triggered an exception (A database query error has occurred. Did you forget to run your application's database schema updater after upgrading? Query: DELETE FROM `wb_terms` WHERE term_language = 'ro' AND term_type = 'description' AND term_text = 'format Wikimedia' AND term_full_entity_id = 'Q14403615' Function: Wikibase\Lib\Store\Sql\TermSqlIndex::deleteTerms Error: 1205 Lock wait timeout exceeded; try restarting transaction (10.64.48.172) ) [Called from Wikibase\Repo\Content\DataUpdateAdapter::doUpdate in /srv/mediawiki/php-1.35.0-wmf.1/extensions/Wikibase/repo/includes/Content/DataUpdateAdapter.php at line 62]
2016 Report
Getting errors like:
Apr 8 09:02:17 mw1342: #012Warning: [data-update-failed]: A data update callback triggered an exception (A database query error has occurred. Did you forget to run your application's database schema updater after upgrading? #012Query: DELETE FROM `wb_terms` WHERE term_language = 'en' AND term_type = 'label' AND term_text = 'Analyzing Cancer Disparities: A New Policy Landscape Calls for New Approaches to Research.' AND term_full_entity_id = 'Q35898854'#012Function: Wikibase\Lib\Store\Sql\TermSqlIndex::deleteTerms#012Error: 1213 Deadlock found when trying to get lock; try restarting transaction (10.64.48.26)#012) [Called from Wikibase\Repo\Content\DataUpdateAdapter::doUpdate in /srv/mediawiki/php-1.31.0-wmf.28/extensions/Wikibase/repo/includes/Content/DataUpdateAdapter.php at line 67] in /srv/mediawiki/php-1.31.0-wmf.28/includes/debug/MWDebug.php on line 309
This happens occasionally:
$ zgrep -cF 'Wikibase\\TermSqlIndex::deleteTerms\nError' archive/hhvm.log-201611* archive/hhvm.log-20161101.gz:0 archive/hhvm.log-20161102.gz:0 archive/hhvm.log-20161103.gz:1 archive/hhvm.log-20161104.gz:1 archive/hhvm.log-20161105.gz:0 archive/hhvm.log-20161106.gz:1 archive/hhvm.log-20161107.gz:0 archive/hhvm.log-20161108.gz:2 archive/hhvm.log-20161109.gz:1 archive/hhvm.log-20161110.gz:0 archive/hhvm.log-20161111.gz:0 archive/hhvm.log-20161112.gz:0 archive/hhvm.log-20161113.gz:2 archive/hhvm.log-20161114.gz:0 archive/hhvm.log-20161115.gz:0 archive/hhvm.log-20161116.gz:1 archive/hhvm.log-20161117.gz:0 archive/hhvm.log-20161118.gz:2 archive/hhvm.log-20161119.gz:0 archive/hhvm.log-20161120.gz:1 archive/hhvm.log-20161121.gz:0 archive/hhvm.log-20161122.gz:3 archive/hhvm.log-20161123.gz:3 archive/hhvm.log-20161124.gz:0 archive/hhvm.log-20161125.gz:3 archive/hhvm.log-20161126.gz:1 archive/hhvm.log-20161127.gz:3
This could probably be solved or at least severely eased by collecting primary keys first (maybe even from a replica) and later on deleting by PK (in TermSqlIndex::deleteTerms and TermSqlIndex::deleteTermsOfEntity)