-
Notifications
You must be signed in to change notification settings - Fork 307
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
Comments
Hitting this issue as well. I think by making the following variable configurable could resolve the issue.
|
Any update on these changes? |
Same issue with https://github.com/awslabs/logstash-output-amazon_es - ideally this should be configurable. |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: