Read mode: sincedb write for XXL files only happens at the end of the file. #195
Assignees
Labels
Comments
guyboertje
pushed a commit
that referenced
this issue
Jun 12, 2018
…#196) * In read mode, request sincedb disk flush on each read loop iteration. The actual write occurs at the `sincedb_write interval`. Note: the chunk size vs the events-per-second affect how often a request is made. e.g. a large chunk size (1MB), lines of say 128 bytes and 256 events/s means each iteration takes 32 seconds, and an eps of 32768 takes 250 ms. * changelog and version bump * make spec a tad more reliable. * add a reference to watch so we can react to quit in the read loop * remove immediate write and add a call to write in the discover/stat loop Fix #195
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
As the sincedb write is only triggered at the end of a large file, if LS is forced to restart, reading begins at the beginning of the file because there is no recorded position for the file.
The text was updated successfully, but these errors were encountered: