Page MenuHomePhabricator

Bring back the req. timeouts without cancelling the cpu timeout
Closed, ResolvedPublic

Description

Quoting @ssastry steps from irc,

  1. no req timeouts (current master after the merge); reduce cpu timeouts to a smaller value .. say 2 minutes .. restbase will retry those requests which would fail again
  2. req timeouts at 110s; they don't remove the cpu timeouts; cpu timeouts at say 2 minutes or a little higher .. restbase will not retry those requests
  3. req timeouts at 110s; we solve the problem of not having a mechanism to halt the wt2html pipeline; and cpu timeouts exist to deal with the runaway cpu computation scenario

Event Timeline

Arlolra claimed this task.
Arlolra raised the priority of this task from to Medium.
Arlolra updated the task description. (Show Details)
Arlolra added projects: Parsoid, Parsoid-Web-API.
Arlolra added a subscriber: ssastry.

While we're at it, the cpu timeout can potentially be moved earlier in the middleware chain, so that it sets as early as possible.

Change 387458 had a related patch set uploaded (by Arlolra; owner: Arlolra):
[mediawiki/services/parsoid@master] T123446: Bring back request timeouts

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

Change 387458 had a related patch set uploaded (by Arlolra; owner: Arlolra):
[mediawiki/services/parsoid@master] T123446: Bring back request timeouts

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

Change 387458 merged by jenkins-bot:
[mediawiki/services/parsoid@master] T123446: Bring back request timeouts

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

This issue is still referenced here: https://github.com/wikimedia/parsoid/blob/master/lib/api/routes.js#L152

Is the process.exit going to be removed? It's causing issues in MWOffliner

Is the process.exit going to be removed? It's causing issues in MWOffliner

No, it's still used if parsoidConfig.useWorker is false. See,
https://github.com/wikimedia/parsoid/blob/master/lib/api/routes.js#L138

Can you elaborate on the issue?