You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Despite the Tailer being launched on a separate thread, @aionWilliam and I have both observed some odd behaviour related to the Tailer when the main execution thread sleeps. Sleeping seems to have caused the Tailer to begin reading from the start of the file again, and seems to make it unable to read past the latest line before the sleep.
The problem is either in the Tailer or else could be related to how the node's output buffer is being flushed to the file or something of the sort.
We need to investigate this further.
The text was updated successfully, but these errors were encountered:
This is really not a priority for the current milestone. @aionWilliam's decision to set the tailer's delay to 2 seconds seems to be sufficient for our purposes. Once we get some time to pursue this question, we want to answer the following:
Why does the tailer start reading again from the top of the file?
What is the optimal delay range in terms of throughput
Note that we are considering switching to our own implementation in the future, one that handles a stream instead of a file. So this is low priority for now.
Despite the
Tailer
being launched on a separate thread, @aionWilliam and I have both observed some odd behaviour related to theTailer
when the main execution thread sleeps. Sleeping seems to have caused theTailer
to begin reading from the start of the file again, and seems to make it unable to read past the latest line before the sleep.The problem is either in the
Tailer
or else could be related to how the node's output buffer is being flushed to the file or something of the sort.We need to investigate this further.
The text was updated successfully, but these errors were encountered: