Last modified: 2013-07-12 03:29:10 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 T53053, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 51053 - Avoid timeouts on large articles
Avoid timeouts on large articles
Status: RESOLVED FIXED
Product: Parsoid
Classification: Unclassified
Web API (Other open bugs)
unspecified
All All
: High normal
: ---
Assigned To: Gabriel Wicke
:
Depends on:
Blocks: 50475
  Show dependency treegraph
 
Reported: 2013-07-09 17:40 UTC by Gabriel Wicke
Modified: 2013-07-12 03:29 UTC (History)
2 users (show)

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


Attachments

Description Gabriel Wicke 2013-07-09 17:40:44 UTC
Huge and template-heavy articles like http://en.wikipedia.org/wiki/List_of_Advanced_Dungeons_%26_Dragons_2nd_edition_monsters take longer than the varnish backend timeout of 60 seconds to render currently. VE has a 100-second timeout currently, but even if that times out we should still let the backend finish the rendering so that the next request can use the cached copy.

See also: VE bug 50475.
Comment 1 Gerrit Notification Bot 2013-07-09 17:41:22 UTC
Change 72681 had a related patch set uploaded by GWicke:
Increase Parsoid backend timeout to 5 minutes

https://gerrit.wikimedia.org/r/72681
Comment 2 Gabriel Wicke 2013-07-10 18:01:17 UTC
The increased timeout is now deployed. Editing http://en.wikipedia.org/wiki/List_of_Advanced_Dungeons_%26_Dragons_2nd_edition_monsters works on second try. The client connection times out the first time (probably the 100 second timeout), but on retry the by-then cached copy is returned.

Needs additional testing on really large pages that take close to 5 minutes to render. It is not clear that Varnish will continue with the request if the client connection was dropped before the page is done.
Comment 3 Gabriel Wicke 2013-07-12 03:29:10 UTC
I will continue to monitor the Varnish logs for timeouts, but so far things are looking good. Resolving as fixed.

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


Navigation
Links