-
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
metricbeat: using all of a single core #2747
Comments
This is probably the thread taking the CPU:
@kevinkluge to guide us during reproducing, did you suspend to ram during that time? |
Ok, that gosigar function is missing some error checks, which could explain an infinite loop. I'm going to do some refactoring on it. I couldn't reproduce the issue yet on my computer, but i didn't upgrade to Sierra yet. |
Errors were ignored in fairly dangerous places, which could result in infinite loops. Potential fix for elastic/beats#2747.
In an attempt to fix elastic#2747.
In an attempt to fix elastic#2747.
@kevinkluge I never could reproduce this on my computer, even after upgrading to Sierra. Would it be possible to try the latest build and see if this seems fixed? I do hope it was caused by the bad error handling, which is fixed by the referenced PRs. Thanks! |
@tsg I've been running the latest metricbeat for a few hours on my laptop without seeing 100% cpu. I'll leave metricbeat running and re-open this issue if I see the problem again. Otherwise, I assume it's fixed as well as it was easily reproducible for me with the earlier build. |
In an attempt to fix elastic#2747.
Version 5.0.0 RC1
MacOS 10.12
With local kibana 5.0 RC1 and Elasticsearch 5.0 RC1, I started Kibana, then ES, then imported metricbeat dashboard, then started metricbeat. After 30-60 minutes, metricbeat was taking all of a single core. I used the default configuration. Nothing unusual was in the logs.
I killed metricbeat with SIGQUIT and got the following.
The text was updated successfully, but these errors were encountered: