Page MenuHomePhabricator

Avoid timeouts on large articles
Closed, ResolvedPublic


Huge and template-heavy articles like 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.

Version: unspecified
Severity: normal



Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 2:05 AM
bzimport added a project: Parsoid-Web-API.
bzimport set Reference to bz51053.

Change 72681 had a related patch set uploaded by GWicke:
Increase Parsoid backend timeout to 5 minutes

The increased timeout is now deployed. Editing 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.

I will continue to monitor the Varnish logs for timeouts, but so far things are looking good. Resolving as fixed.