Windows - file input - sincedb / start_position is ignored
Description
discovered while testing
testing discovered
Gliffy Diagrams
Activity
Philippe Weber February 25, 2015 at 5:27 AM
New input-file plugin with better windows support will ship with logstash 1.5.0RC1
Jason Kendall April 17, 2014 at 6:12 PM
Waiting on new Filewatch release from Jordan.
John Arnold January 14, 2014 at 8:27 PM
submitted pull request https://github.com/jordansissel/ruby-filewatch/pull/27
bob smith January 14, 2014 at 12:57 PM
Yea, there is a difference between the gem included in logstash and the source code for that gem on github. The logstash devs are the only ones that can answer that one really. My patch just used the available source on github for that gem. Good news is that the pull request was merged to master of that gem (which did not modify that particular line), so hopefully soon it will be in the nightly and patching won't be needed anymore.
John Arnold January 14, 2014 at 2:59 AM
Also, I've been playing with the values, and it seems that at very high numbers (128k+) you can get really good read performance but I also get long lulls as well – like the source server is stalling. I'm happy with 32k right now, as I still get lulls but they are shorter and less frequent. If anyone has a theory on that speak up. Otherwise I'll try to wireshark it and check TCP.
Details
Assignee
João DuarteJoão DuarteReporter
Markus HartmannMarkus HartmannLabels
Fix versions
Affects versions
Details
Details
Assignee
João DuarteReporter
Markus Hartmann
I am using a file input on Windows with the latest logstash master version (currently 1.2.3), to parse Log-Files from IIS.
After several tests on Linux and Windows, I realized that if logstash is (re-) started on Windows, all logs are parsed from the beginning again. It does not matter if I set a start_position or an since_db path, or an combination of both, the setting will be ignored.