Last modified: 2014-08-19 13:57:47 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 T71713, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 69713 - Trying to read old log entries times out initially; both API and Special:Log
Trying to read old log entries times out initially; both API and Special:Log
Status: NEW
Product: MediaWiki
Classification: Unclassified
Logging (Other open bugs)
1.24rc
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-08-18 19:53 UTC by Lupo
Modified: 2014-08-19 13:57 UTC (History)
0 users

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


Attachments

Description Lupo 2014-08-18 19:53:55 UTC
I get "504 Gateway Time-out" (no other information, also looked in the page source of that error page) on trying to get the upload log of Sep 30, 2013 at the Commons:

https://commons.wikimedia.org/w/index.php?title=Special:Log&offset=20130930000000&limit=50&type=upload

Unsurprisingly, the API has the same problem:

https://commons.wikimedia.org/w/api.php?action=query&list=logevents&letype=upload&lestart=20130930000000&format=jsonfm

Even the API returns a bland "504 Gateway Time-out" HTML page.

Re-trying the timed-out query (either Special:Log or the API call) again may then succeed, sometimes only after several re-tries. However, the answer still takes very long to compute.

May be difficult to reproduce. It happened to me yesterday, until it suddenly started to work. So I thought it was a spurious effect and did not yet file a bug report. However, today exactly the same thing happened, so here's the bug report.

Looks like something gets cached and takes very long getting cached, so the first few attempts time out. But once the thing (whatever it is, a database index?) is cached, subsequent queries work, also for other dates in the vicinity of the initial date. That would at least explain the behavior I'm seeing. I presume the cached data gets evicted from the cache after some time, so re-trying the query the next day has to re-cache it and then initially times out again.

Even when it finally works, it's often rather sluggish to return results.

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


Navigation
Links