Hi All We have configured `retry limit 5` and `retry exhaust Fluent Community #fluent-bit

Hi All. We have configured `retry_limit 5` and `re...

Padma

09/02/2026, 10:51 AM

Hi All. We have configured

retry_limit 5

and

retry_exhausted_action delete

for the S3 output. In Fluent Bit 5.0.7 and 5.0.9, buffered files were successfully deleted from

store_dir

once the retry limit was reached. However, after upgrading to 5.1.1,we could see some of the files remain in the buffer path and continue to accumulate. As a result, buffer usage keeps increasing even after the retry limit has been exceeded. We are also unable to use 5.0.7/5.0.9 due to the underflow error issue. Has anyone observed this behaviour in 5.1.1. Can anyone help on this.

Padma

09/02/2026, 10:52 AM

Copy code

[OUTPUT]
        Name                s3
        Match_regex         ^(kubernetes.*)$
        Bucket              ${S3_BUCKET}
        Region              us-east-1
        endpoint            ${S3_ENDPOINT}
        compression         gzip
        s3_key_format       /logs/site_name=${SITE_NAME}/cluster_name=${CLUSTER_NAME}/year=%Y/month=%m/day=%d/hour=%H/minute=%M/v1_%Y%m%d%H%M%S_$UUID.gz
        Upload_chunk_size   50M
        static_file_path    On
        use_put_object      Off
        store_dir           /var/log/fluentbit/log/vcmts/s3/
        store_dir_limit_size   2GB
        storage.total_limit_size 20GB
        retry_limit         5
        retry_exhausted_action delete

hhatake

09/03/2026, 4:42 AM

Hi, I also add commits for mitigating this issue in: github.com/fluent/fluent-bit/pull/12360 This can resolve your issue on your environment?

Padma

09/03/2026, 6:30 AM

If the retry limit is exceeded clearing the chunks happens in store_dir issue will be solved.

Open in Slack

Previous Next