Improve error condition communication from backend#1780
Merged
rashidkpc merged 3 commits intoelastic:masterfrom Nov 5, 2014
Merged
Improve error condition communication from backend#1780rashidkpc merged 3 commits intoelastic:masterfrom
rashidkpc merged 3 commits intoelastic:masterfrom
Conversation
Merged
Contributor
Author
|
@simianhacker any issues with how this was done? |
Member
|
LGTM |
rashidkpc
added a commit
that referenced
this pull request
Nov 5, 2014
Improve error condition communication from backend
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously if the backend was unable to connect to Elasticsearch it would simply throw an "Internal Server Error". This change sets the HTTP status to 502 (bad gateway) or 504 (gateway timeout) depending on Elasticsearch's availability. It also communicates that in the fatal message.