On Mon, Nov 28, 2011 at 12:21 AM, Asher Feldman
<afeldman(a)wikimedia.org>
wrote:
That page wasn't suitable for high volume
public consumption (very
expensive db query + not properly cached), so the site problem persisted
even after the db initially suspected as bad was rotated out.
What happened to it? When this page was introduced, it did have proper
caching in memcached. Was that removed? Or did we get a cache
stampede?
I asked roughly the same thing yesterday (more along the lines of "shouldn't
it take someone ten minutes to add memcache support to the extension?").
Reedy said it was long-running queries that never timed out that apparently
caused the issue.
The ContributionReporting extension being disabled is being tracked here:
<https://bugzilla.wikimedia.org/show_bug.cgi?id=32679>.
MZMcBride