Skip to content
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

stomp collector bot constantly uses 100% of CPU #1364

Closed
ghost opened this issue Dec 19, 2018 · 8 comments
Closed

stomp collector bot constantly uses 100% of CPU #1364

ghost opened this issue Dec 19, 2018 · 8 comments
Labels
bug Indicates an unexpected problem or unintended behavior component: bots
Milestone

Comments

@ghost
Copy link

ghost commented Dec 19, 2018

As the title says, I have noticed that on both our testing and production environment the stomp collector bot is constantly taking very high CPU percentage even when it is idle. Has anyone else experienced the same issue?

@ghost
Copy link

ghost commented Jan 9, 2019

As we do not get any data via stomp currently, I can't test it. However it didn't attract my attention in the past.

@ghost ghost added bug Indicates an unexpected problem or unintended behavior component: bots labels Jan 9, 2019
@ghost ghost modified the milestones: 1.1.1, 1.1.2 Jan 9, 2019
@ghost
Copy link

ghost commented Mar 25, 2019

What do you have as rate_limit parameter?

@ghost ghost modified the milestones: 1.1.2, 1.2.0 Mar 25, 2019
@ghost
Copy link
Author

ghost commented Mar 28, 2019

Nothing. We do not have this parameter set (and I could not find any default value).

@ghost
Copy link

ghost commented Mar 28, 2019

It should be in the defaults.conf

@ghost
Copy link
Author

ghost commented Mar 28, 2019

Right, sorry, I went there before and somehow missed it.
"rate_limit": 0

@ghost
Copy link

ghost commented Mar 28, 2019

Please try if setting this parameter to a non-zero value helps (for this bot only to not affect your other bots)

@ghost ghost modified the milestones: 1.2.0, 2.0.0 Apr 9, 2019
@ghost
Copy link
Author

ghost commented Apr 15, 2019

Perfect, that did fix the issue. Would it be generally recommendable to put rate_limit > 0 to defaults.conf?

Sorry it took so long.

@ghost ghost closed this as completed in 9d4f62b May 13, 2019
@ghost
Copy link

ghost commented May 13, 2019

A sane default would indeed by nice, but OTOH that applies to all bots, including parsers, experts and outputs. That's not wanted. So I hardcoded a minimum of 1s rate limit for bots of this kind, without logging. That should solve the issue independent of the configuration.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or unintended behavior component: bots
Projects
None yet
Development

No branches or pull requests

0 participants