Page MenuHomePhabricator

Error 504 Gateway Time-out on Special:Log/INeverCry and others
Closed, ResolvedPublic

Description

Trijnstel reports that for users like INeverCry, Fastily, Túrelio and Herbythyme it's impossible to load Special:Log: it keeps loading and finally timeouts, Error 504 Gateway Time-out by nginx.
Setting a low limit doesn't help, while adding a type filter does, e.g. https://commons.wikimedia.org/w/index.php?title=Special%3ALog&type=block&user=INeverCry

Those are all users with tens of thousands log entries.


Version: 1.22.0
Severity: major
URL: https://commons.wikimedia.org/wiki/Special:Log/INeverCry?limit=1
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=39508

Details

Reference
bz54876

Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 2:33 AM
bzimport set Reference to bz54876.
bzimport added a subscriber: Unknown Object (MLST).

Change 87168 had a related patch set uploaded by Aaron Schulz:
Removed more FORCE INDEX clauses for logging

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

Change 87168 merged by jenkins-bot:
Removed more FORCE INDEX clauses for logging

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

Is more work needed or can this be closed after Aaron's patch got merged?

(In reply to comment #3)

Is more work needed or can this be closed after Aaron's patch got merged?

Don't know. I only know that I also see this happen on another wiki, nlwiki.

Could someone please fix this? It's quite a major bug.

(In reply to comment #6)

Could someone please fix this? It's quite a major bug.

I'm confused, the fix was made live yesterday on Commons few minutes before you wrote this comments and the example URL works; marking fixed, please reopen if it's not.
In 2 days this will land on Wikipedias too.

(In reply to comment #7)

(In reply to comment #6)

Could someone please fix this? It's quite a major bug.

I'm confused, the fix was made live yesterday on Commons few minutes before
you
wrote this comments and the example URL works; marking fixed, please reopen
if
it's not.
In 2 days this will land on Wikipedias too.

Ah, I guess that's why. I checked it on nlwiki when I replied here yesterday.

I don't understand why a fix for this wasn't deployed immediately.