greenwave

#38 Returning a 503 "Service Unavailable" sounds not smart
Closed: Fixed Opened by puiterwijk.

Closed: Fixed
Reopen Issue

If either resultsdb or waiverdb do not respond or time out, not only does nothing get logged (which would be great for debugging purposes!), greenwave returns a 503 error.
In certain cases, this might lead the entire application server to be marked as "unavailable" for an extended period of time.
I would suggest using 502/504 to indicate that the error is in a downstream server, or a plain 500.

Hopefully, those two servers never come down :-). Using 504 sounds good to me and we should definitely lodge the error.

Hopefully, I'll win the lottery tomorrow. I like my chances of that a lot better than your bet.
Edited by puiterwijk

Haha, good luck on your lottery.

PR #43

Metadata Update from @mjia:
- Issue status updated to: Closed (was: Open)

Metadata Update from @dcallagh:
- Issue assigned to mjia
- Issue close_status updated to: Fixed
- Issue set to the milestone: 0.1
Metadata
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.