-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Handle Request Entity Too Large errors in ElasticSearchOutput
If we try to bulk index a batch of messages that exceeds the elastic search `bulk_max_body_size` setting. (default 100MB) Elastic will respond with an HTTP 413 Entity Too Large error. In this case we retry the request by splitting the message batch in half. When responding with an HTTP 413 error, the server is allowed to close the connection immediately. This means that our HTTP client (Jest) will simply report an IOException (Broken pipe) instead of the actual error. This can be avoided by sending the request with an Expect-Continue header, which also avoids sending data that will be discarded later on. Fixes #5091
- Loading branch information
Showing
3 changed files
with
146 additions
and
28 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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