-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
packetbeat starts logging errors with too many open files watching processes with -beta4 #335
Comments
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this issue
Oct 26, 2015
…olang garbage collector automatically closes the FD associated with os.File which is why the FD count didn't grow completely unbounded; in my testing the FD count would cyclically grow to about ~500 and then drop back down to ~5. Close elastic#335
Closed
tsg
pushed a commit
to tsg/beats
that referenced
this issue
Jan 20, 2016
…olang garbage collector automatically closes the FD associated with os.File which is why the FD count didn't grow completely unbounded; in my testing the FD count would cyclically grow to about ~500 and then drop back down to ~5. Close elastic#335
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With 1.0.0-beta4, RHEL 7.1, 4 socket, 40 CPUs, 256 GB of memory ...
When I looked the open files, and this one packetbeat instance has close to 500+ /proc files opened. Here are the logs from /var/log/message from one second:
The text was updated successfully, but these errors were encountered: