Skip to content
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

Too large payload responses (413) are not being properly handled #1180

Open
edmocosta opened this issue May 30, 2024 · 0 comments
Open

Too large payload responses (413) are not being properly handled #1180

edmocosta opened this issue May 30, 2024 · 0 comments

Comments

@edmocosta
Copy link
Contributor

edmocosta commented May 30, 2024

Logstash is crashing with OOM when documents are bigger than the Elasticsearch http.max_content_length. Those documents are filling up the memory and are never freed due to infinite retries.

it seems there’s a clear intention to handle 413 status here, which is not working properly due to the manticore's adapter logic. This adapter raises an error, making the http_client condition unreachable, leading to infinite retries and no options to DLQ those problematic events (dlq_custom_codes).


Relates to: #785

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant