-
Notifications
You must be signed in to change notification settings - Fork 77
Decrease fluent-bit buffer_max_size to 2M for smaller outgoing requests. #867
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
Thanks. The Windows integration test failure was a flake. Merging. |
|
Shall we also add a test case with a log entry really big and see it didn't get the API denied response? 🤔 |
I think the issue here is that the accumulated size of the log entries exceeds the API request limit. A single entry will still be rejected, as it'd be over the entry size limit (256k). While we can try to simulate the "multiple entries add up to a request that's too large" scenario, it seems very fragile and hard to reproduce, so the test will likely be flaky. |
Description
Some outgoing requests end up being over the API limit. This PR reduces the chance of that happening by lowering the maximum size of the accumulated buffer.
Related issue
http://b/244498953
How has this been tested?
Only automatic unit tests.
Checklist: