Last modified: 2013-07-12 17:52:12 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 T52785, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 50785 - Unintended job queue lag due to template null edits, API action=purge
Unintended job queue lag due to template null edits, API action=purge
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
JobQueue (Other open bugs)
unspecified
All All
: High normal (vote)
: 1.22.0 release
Assigned To: Tim Starling
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-05 04:39 UTC by Tim Starling
Modified: 2013-07-12 17:52 UTC (History)
3 users (show)

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


Attachments

Description Tim Starling 2013-07-05 04:39:43 UTC
Wikimedia users routinely do null edits when they feel the job queue is not fast enough for their needs. Unfortunately, null edits of templates cause refreshLinks jobs to be queued, which exacerbates the problem they were intending to solve. In the current case, a user null-edited several templates, causing the equivalent of 22 million page parse operations to be queued.

In a previous case, a user caused permanent job queue lag with a bot which regularly executed API action=purge with forcelinkupdate=1, not realising that the updates would be recursive.

I suggest making null edits do only non-recursive link updates, and I suggest splitting the forcelinkupdate API parameter into forcelinkupdate and forcerecursivelinkupdate.
Comment 1 Tim Starling 2013-07-05 05:02:39 UTC
https://gerrit.wikimedia.org/r/#/c/72064/
Comment 2 Umherirrender 2013-07-12 17:52:12 UTC
change set is successfully merged

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


Navigation
Links