Unintended job queue lag due to template null edits, API action=purge
Closed, ResolvedPublic


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.

Version: unspecified
Severity: normal

bzimport set Reference to bz50785.
tstarling created this task.Via LegacyJul 5 2013, 4:39 AM
Umherirrender added a comment.Via ConduitJul 12 2013, 5:52 PM

change set is successfully merged

Add Comment

Column Prototype
This is a very early prototype of a persistent column. It is not expected to work yet, and leaving it open will activate other new features which will break things. Press "\" (backslash) on your keyboard to close it now.