Closed
Bug 759527
Opened 13 years ago
Closed 13 years ago
aitc: increase zeus/nginx/gunicorn timeouts from the current 30 seconds
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Atoll, Assigned: Atoll)
Details
(Whiteboard: [qa-])
Define a better timeout for aitc than 30 seconds, then implement it on the z/n/g stack and document in AITC's ZeusSetup page.
+++ This bug was cloned on behalf of Ryan Kelly [:rfkelly], per bug 756925#c5:
> This is happening again on at least aitc1.web.scl2.stage.svc.mozilla.com,
> this time when zeus terminate a request that has taken longer than 30
> seconds to complete. For example:
>
> 10.14.214.201 - - [28/May/2012:22:59:14 -0700] "GET /1.0/757095/apps/
> HTTP/1.0" 499 0 "-" "-" XFF="63.245.208.248" TIME=31.937
> 10.14.214.201 - - [28/May/2012:22:59:14 -0700] "GET /1.0/757095/apps/
> HTTP/1.0" 401 21 "-" "-" XFF="63.245.208.248" TIME=0.003
>
> The 499 response is nginx logging the fact that zeus disconnected before the
> request could complete; the 401 error is an auth failure caused by something
> retrying the failed request.
Stage and SCL2 timeouts for AITC are now 560/575/600 seconds (gunicorn/nginx/zeus), to match Sync. Documented at https://intranet.mozilla.org/Services/Ops/AITC/ZeusConfig#Queuing
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Whiteboard: [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•