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

out_http: don't retry non retryable 4xx status codes #8861

Merged
merged 1 commit into from
Jul 8, 2024

Conversation

IsraelZeromski
Copy link
Contributor

Fix a problem that http output plugin retries all requests that respond with an 4xx status code excepting 429 status code

Fixes #8860


Enter [N/A] in the box, if an item is not applicable to your change.

Testing
Before we can approve your change; please submit the following in a comment:

  • [N/A] Example configuration file for the change
  • [N/A] Debug log output from testing the change
  • [N/A] Attached Valgrind output that shows no leaks or memory corruption was found

If this is a change to packaging of containers or native binaries then please confirm it works for all targets.

  • [N/A] Run local packaging test showing all targets (including any new ones) build.
  • Set ok-package-test label to test for all targets (requires maintainer to do).

Documentation

  • [N/A] Documentation required for this feature

Backporting

  • Backport to latest stable release.

Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

Fix a problem that http output plugin retries all requests that respond with an 4xx status code excepting 429 status code

Signed-off-by: Israel Zeromski <izeromski@salesforce.com>
flb_plg_warn(ctx->ins, "could not flush records to %s:%i (http_do=%i), "
"chunk will not be retried",
ctx->host, ctx->port, ret);
out_ret = FLB_ERROR;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does that mean logs will be lost when the endpoint is unavailable?

Copy link
Contributor Author

@IsraelZeromski IsraelZeromski May 24, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. if return a code in 4xx range except 429, this means that the are an error in client side in consequence that records will not be retry.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fluentd has a setting for retryable response codes: https://docs.fluentd.org/output/http#retryable_response_codes maybe we could add this as well?

@edsiper edsiper added this to the Fluent Bit v3.0.7 milestone May 29, 2024
@edsiper edsiper merged commit 4dfc256 into fluent:master Jul 8, 2024
44 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

out_http: don't retry non retryable 4xx status codes
3 participants