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
Bug: file plugin does not always read files from the beginning dispite start_position=beginning #173
Comments
fbaligand
changed the title
File first lines are - sometimes - not read
Bug: file plugin does not always read files from the beginning dispite start_position=beginning
Mar 28, 2018
Same problem reported in LS repo. elastic/logstash#8929 |
Await feedback on whether |
Hi @guyboertje, I will make tests this week with file input version 4.1.0 to check if it fixes the issue. Fabien |
Hi @guyboertje ,
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I configure file input to read all files in a folder from the beginning, I notice that not all files are read from the beginning. For example, some files are read from line 306, all previous lines are not read, and so, lost.
This is really annoying, because we can't rely on this plugin behavior.
The problem seems to happen when there are lots of files (more than 500).
Up to my tests, it is tied to sincedb file size. When it becomes too big, new files that arrive are not read from beginning, sometimes, even not read at all.
If I drop sincedb file, and I restart Logstash, it works fine during some days, until sincedb file becomes big again.
My guess about that bug fix is to remove from sincedb file, files that are older than
ignore_older
option.Logstash version : 6.1.3
file input configuration :
The text was updated successfully, but these errors were encountered: