Closed
Bug 1221806
Opened 9 years ago
Closed 9 years ago
Gunicorn should use a timeout shorter than 120s on stage/prod
Categories
(Tree Management :: Treeherder: Infrastructure, defect, P1)
Tree Management
Treeherder: Infrastructure
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Assigned: emorley)
References
Details
Attachments
(1 file)
It may help prevent things like bug 1211415 if we use a shorter timeout than the current 120s one for the Treeherder API.
Heroku has a 30s cutoff for requests, and so we already have a 29s timeout set in gunicorn there, so in theory it shouldn't cause issues. (We can test on stage).
|
Assignee | |
Comment 1•9 years ago
|
||
Attachment #8683382 -
Flags: review?(mdoglio)
|
||
Updated•9 years ago
|
Attachment #8683382 -
Flags: review?(mdoglio) → review+
|
||
Comment 2•9 years ago
|
||
Commit pushed to master at https://github.com/mozilla/treeherder
https://github.com/mozilla/treeherder/commit/50cec5c1fe71a04c0f8da0bef87783bd9ad621c8
Bug 1221806 - Change the stage/prod Gunicorn timeout from 120s to 30s
To help prevent excessively demanding queries from having a detrimental
effect on the API/DBs.
|
|
Assignee | |
Updated•9 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•