Last modified: 2014-06-30 13:34:41 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T58776, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 56776 - Recent changes table locked and causing "Database error" when many deletions happen
Recent changes table locked and causing "Database error" when many deletions ...
Status: VERIFIED FIXED
Product: MediaWiki
Classification: Unclassified
Recent changes (Other open bugs)
1.23.0
All All
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-08 13:53 UTC by Stryn
Modified: 2014-06-30 13:34 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Stryn 2013-11-08 13:53:44 UTC
See https://www.wikidata.org/wiki/Wikidata:Contact_the_development_team/Archive/2013/10#Database_error_when_deleting_items_too_fast

When I'm deleting items on Wikidata too fast (many items within short timeframe), I get a database error. I'm using a "flooder" user group.

A database query error has occurred. This may indicate a bug in the software.

Function: RecentChange::save

Error: 1213 Deadlock found when trying to get lock; try restarting transaction (10.64.32.28)

See especially the last comment by Adam Shorland (WMDE).
Comment 1 Umherirrender 2013-11-08 18:22:41 UTC
RecentChanges::save is also called for flooders, because also actions by flooders are in the recent changes, there are only marked as bot and therefor needs change of the filter to show bot edits. Same for watchlist.
Comment 2 Stryn 2014-01-28 17:29:00 UTC
Today I got the same error message on the Finnish Wikipedia, so it's not related to Wikidata nor flooders user group.
Comment 3 Aaron Schulz 2014-06-10 19:04:41 UTC
I see this on Commons, likely due to FileDeleteForm calling doDeleteArticleReal(), telling it to keep the transaction open and then deleting the file (slow) and committing afterwards.
Comment 4 Gerrit Notification Bot 2014-06-10 20:26:58 UTC
Change 138677 had a related patch set uploaded by Aaron Schulz:
Reduce deadlocks adding log rows to the RC table on delete

https://gerrit.wikimedia.org/r/138677
Comment 5 Gerrit Notification Bot 2014-06-11 18:45:44 UTC
Change 138677 merged by jenkins-bot:
Reduce deadlocks adding log rows to the RC table on delete

https://gerrit.wikimedia.org/r/138677

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links