Hello. We have the store_dir_limit space available...
# fluent-bitp
Padma
09/30/2026, 10:54 AMHello. We have the store_dir_limit space available but we could still see buffer path full.
Padma
09/30/2026, 10:54 AM Copy code
[2026/09/29 18:25:02] [error] [output:s3:s3.1] Buffer is full: current_buffer_size=1999999903, new_data=1261, store_dir_limit_size=2000000000 bytes
[2026/09/29 18:25:02] [error] [output:s3:s3.1] Buffer is full: current_buffer_size=1999999903, new_data=7279, store_dir_limit_size=2000000000 bytes
[2026/09/29 18:25:02] [error] [output:s3:s3.1] Buffer is full: current_buffer_size=1999999903, new_data=2390, store_dir_limit_size=2000000000 bytesPadma
09/30/2026, 10:55 AMAny reason why we are getting this case
p
Pat
09/30/2026, 11:04 AMWhat's your config, version, etc.?
p
Padma
09/30/2026, 12:52 PMVersion 3.0.4
p
Pat
09/30/2026, 12:52 PMok, that's very old...
Pat
09/30/2026, 12:56 PMrelated to github.com/fluent/fluent-bit/issues/12164?
p
Padma
09/30/2026, 1:06 PMIssue says it is not seen in earlier of 5.0,6 but we are facing issue
Padma
09/30/2026, 1:07 PMIs there a way to cleanup the files on store_dir when restart happens
p
Pat
09/30/2026, 1:07 PMit won't be fixed if you're seeing it in anything older then 5.0 series: github.com/fluent/fluent-bit/security/policy
Pat
09/30/2026, 1:07 PMsure, add a prelaunch script that does it via systemd or whatever
Pat
09/30/2026, 1:09 PM3.0.4 is May 2024, there is a 3.0.7 so might be worth trying that
Pat
10/01/2026, 9:41 PMand github.com/fluent/fluent-bit/discussions/12261 might also be actually relevant too, note it indicates the fix is in the 5.1 series
2 Views