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

V2.2.2 / AWS S3 Output Plugin / retry_limit not taken into account #8595

Closed
JSchy65 opened this issue Mar 18, 2024 · 2 comments · May be fixed by #8985
Closed

V2.2.2 / AWS S3 Output Plugin / retry_limit not taken into account #8595

JSchy65 opened this issue Mar 18, 2024 · 2 comments · May be fixed by #8985

Comments

@JSchy65
Copy link

JSchy65 commented Mar 18, 2024

Fluent Bit Version 2.2.2 Jan. 15 2024
AWS S3 Output Plugin, https://docs.fluentbit.io/manual/pipeline/outputs/s3

For the Configuration Parameter retry_limit the documentation says:
"Integer value to set the maximum number of retries allowed. Note: this configuration is released since version 1.9.10 and 2.0.1. For previous version, the number of retries is 5 and is not configurable."

This is not true. For 2.2.2 that parameter is also not taken into account. Instead, the fixed value MAX_UPLOAD_ERRORS=5 is used.

I kindly ask you to update the 2.2.x code in a way, that it takes this parameter into account. Otherwise, that version will not be usable in environments, where network connection is often lost for more than 100s (*), e.g. edge device scenarios.

Related:
#6475

(*) put object: MAX_UPLOAD_ERRORS=5 x2 x10s = 100s
The x2 seems also to be fixed implemented and also the retry time of 10s.

Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.

Copy link
Contributor

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant