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-1.3.1-x86_64 Out Of Memory #2867
Comments
A few question:
|
|
I start packet beat Last night to send event to my log server via logstash output ,and ...it crash again ,here is my log
|
Have you tried with packetbeat 5.0 release as well? in packetbeat 5.0 amount of events stored in memory in backpressure is configurable via Do you have some means to monitor memory usage? |
I think i found the problem ,the first hour ,packetbeat is run very well,it publish 5w events to my server,but in next hour,it send nerly 100w event which all of mongo package to my logserver,and it crash |
here is why packetbeat oom....https://my.oschina.net/xiaomaijiang/blog/782496?from=groupmessage&isappinstalled=0 |
closing it, the problem is caused by |
Please post all questions and issues on https://discuss.elastic.co/c/beats
before opening a Github Issue. Your questions will reach a wider audience there,
and if we confirm that there is a bug, then you can open a new issue.
For confirmed bugs, please report:
Here is My PacketBeat config
Here is The Error Log
Additionaly,I run filebeat(master) and metricbeat(master) on this machine too,and both of this beat killed by operation system too. it is strange
The text was updated successfully, but these errors were encountered: