This repository has been archived by the owner on Apr 2, 2024. It is now read-only.
Add a configuration option to the logstreamer input for the "check for more data" interval #1841
Comments
|
in my config in #1626 I have single log file in logstreamer config to listen to and still have same issue. If this matters. |
simonpasquier
pushed a commit
to simonpasquier/heka
that referenced
this issue
Feb 23, 2016
This change addresses the issue mozilla-services#1841. To avoid excessive CPU usage, users can set a value higher than the default 250ms when they know that a single logstreamer input may process many log files.
simonpasquier
pushed a commit
to simonpasquier/heka
that referenced
this issue
Feb 24, 2016
This change addresses the issue mozilla-services#1841. To avoid excessive CPU usage, users can set a value higher than the default 250ms when they know that a single logstreamer input may process many log files.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As noted by @elemoine on the mailing list, a single logstreamer instance monitoring many files may increase dramatically the CPU load of the system. This is because the logstreamer plugin checks every 250ms if there's more data to collect and the value is hardcoded.
The idea would be have a configuration option to set the "check for more data" interval with a default value of 250ms.
The text was updated successfully, but these errors were encountered: