-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
pos file cleanup #3488
Comments
If you have problems in v1.14.0.rc, please let me know. I'll reopen this. |
Thank you for the quick response. I am using docker fluentd. Do you know if there are plans to update version 1.13? |
v1.14.0 isn't released yet, it's currently RC (release candidate) state. |
Describe the bug
Hi,
I am trying to understand how the fluentd pos file cleanup happens.
At the moment, I am using docker image of fluentd version 1.11.5-1.0, but I have also tried version 1.13.0-1.0.
Here is a sample conf file I have:
I am finding that when the compaction runs to clean up the pos file, if the file was deleted while fluentd was stopped and not running, that while expect the line to be removed from the pos file on fluentd startup or on compaction, neither happens and the line will be there forever as it seems that fluentd will no longer ever clean up that line.
I also found that if i change the file pattern in path, I expect on restart of fluentd that files that no longer match the pattern should be removed from the pos file. I am finding that this is not the case.
My concern is clean ups of pos file will not happen in the two above scenarios and my pos file will just keep growing with time.
To Reproduce
Scenario 1
Scenario 2
The only scenario where pos file cleanup happens correctly is when fluentd is running and files are deleted or renamed while fluentd is running.
Expected behavior
Pos file on restart of fluentd and run of compaction should clean up all files that no longer exist and ones that do not match path pattern.
Your Environment
Your Configuration
Your Error Log
Additional context
No response
The text was updated successfully, but these errors were encountered: