serve 503s when nginx has a 499

RESOLVED FIXED

Status

Cloud Services
Operations
RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: petef, Assigned: atoll)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

7 years ago
Right now when Zeus times out talking to a sync backend, it disconnects from nginx (which logs a 499), and sends a 200 back to the client with an empty body. We should really be serving 503s here.
These should probably also be hitting some alert aggregation, too...
OS: Linux → All
Hardware: x86_64 → All
See Also: → bug 667060
(In reply to comment #1)
> These should probably also be hitting some alert aggregation, too...

Multibug detected, please file something under Operations: Monitoring?
(In reply to comment #2)
> Multibug detected, please file something under Operations: Monitoring?

Done: Bug 667588.
Created attachment 544769 [details] [diff] [review]
add 499 to the list of backend node response codes that we convert to 503
applied to { dev, stage, load } and { phx, scl2 }.  verified that we're not seeing any unusual 503s at each site.
Assignee: nobody → rsoderberg
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.