Last modified: 2010-05-15 15:29:35 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 T2237, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 237 - Recentchanges purges cause lock wait timeout
Recentchanges purges cause lock wait timeout
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
1.3.x
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-08-28 02:37 UTC by Jamesday
Modified: 2010-05-15 15:29 UTC (History)
1 user (show)

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


Attachments

Description Jamesday 2004-08-28 02:37:24 UTC
I've observed the periodic deletes from recentchanges taking in excess of 200
seconds at only moderately busy times and lock wait timeouts have been reported
for en Wikipedia with recentchanges specified as the affected table. Perhaps
increasing their frequency would help, by reducing the work per update.

As an interim step I've increased the Wikimedia lock wait timeout value.
Comment 1 Zigger 2005-06-06 19:14:41 UTC
(Set MW Version to 1.3.1 based on report date and release history.)
AFAICT, 1.4 & 1.5 still do this on average every 1000 edits, so with constant
editing, an average of 1000 rows would be deleted each time along with the index
changes.  v1.4 added another index.

Is this still an issue?  Increasing the frequency seems like an easy change to
make, and 1000x seems like a very high factor for removing the overhead.
Comment 2 Antoine "hashar" Musso (WMF) 2005-08-24 20:53:17 UTC
Closing bug as the frequency got increased + we now run
the biggest mediawiki site (en.wikipedia) under 1.6 ;)

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


Navigation
Links