daipom
commented
8 months ago
./worker0
Where is this directory?
Open chrko opened 8 months ago
daipom
commented
8 months ago
./worker0
Where is this directory?
chrko
commented
8 months ago
./worker0Where is this directory?
The buffer file directory structure is located in /application/diagnostics/${tag[0]}/${tag[2]}/${tag[3]}-%Y-%m-%d. This folder contains the folders worker[0-7].
The same pattern is present for the second path template /application/diagnostics/${tag[1]}/${tag[3]}/${tag[1]}-%Y-%m-%d.
daipom
commented
8 months ago Thanks for your report.
I found a bug.
When the buffer path includes [ or ], the resuming process can not find the remaining files.
This is caused by the lack of escapes.
daipom
commented
8 months ago You can avoid this problem by improving the setting.
Currently, you don't set path of buffer.
So, out_file sets the buffer path automatically to out_file's path.
You can set a more simple and safe path for buffer.
chrko
commented
8 months ago @daipom This sounds promising. I'll check out, but unfortunately we couldn't put the story on the topic into the current sprint :disappointed: I'll check in 2 weeks again!
Describe the bug
After restart of fluentd, buffer files from previous runs are not being resumed and instead there for infinite time period. Example directory listing:
To Reproduce
During a continuous stream of events (source doesn't matter), restart fluentd:
Afterwards check the contents of the directory containing the buffer files.
Expected behavior
No files with modification time older than ~5 seconds (the flush interval) / ~1 minute (default resolution of directory listing) should be present in the buffer directories.
Your Environment
Your Configuration
Your Error Log
Additional context
No response