Skip to content

new: fallback host support for 503 errorNum #189

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 30, 2021

Conversation

aMahanna
Copy link
Member

From a discussion with the ArangoDB Java & Go maintainers (cc @rashtao):

please note that failover/retry in case of status 503 should happen only in these cases:
1. the response has body like {"error":true,"errorNum":503,"code":503, ...}, note errorNum=503
2. the 503 response comes from an intermediate proxy, so it does not contain a json body like the one above
Other 503 responses with different errorNum should not lead to failover/retry, but just thrown to the caller.

@aMahanna aMahanna requested a review from joowani December 28, 2021 22:40
@joowani joowani merged commit b448ade into main Dec 30, 2021
@aMahanna aMahanna deleted the feature/fallback-host-for-503-errorNum branch December 30, 2021 22:29
@aMahanna aMahanna self-assigned this Dec 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants