Skip to content

Output fails with 413 Payload Too Large #785

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

Open
msvticket opened this issue Jun 14, 2018 · 3 comments
Open

Output fails with 413 Payload Too Large #785

msvticket opened this issue Jun 14, 2018 · 3 comments
Assignees

Comments

@msvticket
Copy link

Output is failing occasionally since ElasticSearch is giving a http status 413 response with the message {"Message":"Request size exceeded 10485760 bytes"}

The actual error in the log is

[logstash.outputs.elasticsearch] Encountered a retryable error. Will Retry with exponential backof

The ElasticSearch is an AWS Elasticsearch service. AWS is apparently restricting the setting of http.max_content_length 10MB for smaller instance types according to this table:
https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/aes-limits.html#network-limits

@Oktaz
Copy link

Oktaz commented Jul 13, 2018

Hitting this issue as well. I think by making the following variable configurable could resolve the issue.

TARGET_BULK_BYTES = 20 * 1024 * 1024 # 20MiB

@RishikeshDarandale
Copy link

Any update on these changes?

@lifeofguenter
Copy link

Same issue with https://github.com/awslabs/logstash-output-amazon_es - ideally this should be configurable.

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 a pull request may close this issue.

5 participants