You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
The text was updated successfully, but these errors were encountered: