bugtask:+index Timeout (lots of comments and attachments)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Robert Collins |
Bug Description
[Problem]
Bug #317094 has been consistently generating a HTTP Error 503: Service Unavailable over the last week when running a script that processes its attachments.
[Discussion]
Cronned runs of process-
This bug report has over 200 comments, and also has an unusually large number of attachments from a range of different people. I notice if I try to view all the comments from the web interface it times out after a few moments. (I tested both edge and production.)
I think it's fairly well known that bugs with >400 comments tend to time out, but ones with only 216 comments generally are okay. So I'm more wondering if it has something to do with the large number of attachments on this bug report.
When accessing the comments from the web interface, the Oops looks like this
Timeout error
Sorry, something just went wrong in Launchpad.
We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience.
Trying again in a couple of minutes might work.
(Error ID: OOPS-1601G2848)
Traceback (most recent call last):
* Module zope.publisher.
...
* Module canonical.
connection, raw_cursor, statement, params)
* Module storm.tracer, line 49, in connection_
TimeoutError: 'SELECT LibraryFileCont
SQL time: 5202 ms
Non-sql time: 15510 ms
Total time: 20712 ms
Statement Count: 506
no long sql statements here - there is however a big jump:
348. 8717 44ms launchpad-
349. 15868 62ms launchpad-
That is, between getting the attachment data, and starting onto tags, there is a 5 second 'nonsql' gap - could be talking to librarian or something I guess.
affects: | launchpad → malone |
description: | updated |
tags: |
added: qa-ok removed: qa-needstesting |
summary: |
- Timeout accessing bug with lots of comments and attachments + bugtask:+index Timeout (lots of comments and attachments) |
Changed in malone: | |
status: | Fix Committed → Fix Released |
Here is the output from the cron job, showing the error page returned to the script, and a Traceback.