API collector: high CPU load even if no message are processed #2108
Labels
Milestone
Comments
ghost
added
bug
ghost
self-assigned this
ghost
pushed a commit
that referenced
this issue
Sep 9, 2021
Make private members `__is_multithreadable` and `__collector_empty_process` protected members `_is_multithreadable` and `_collector_empty_process` to make them easily modifiable by Bot classes fixes #2108
ghost
pushed a commit
that referenced
this issue
Sep 9, 2021
Make private members `__is_multithreadable` and `__collector_empty_process` protected members `_is_multithreadable` and `_collector_empty_process` to make them easily modifiable by Bot classes fixes #2108
ghost
mentioned this issue
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The API collector is consuming a lot of CPU, up to 100%, independent of the actual message load. strace shows, that the bot is always polling redis, for the stats (which are written after the
processexecution).The problem is, that the bot declares
intelmq/intelmq/bots/collectors/api/collector_api.py
Line 40 in f2b07f6
but this attribute is part of the
Botclass:intelmq/intelmq/lib/bot.py
Line 114 in f2b07f6
and should therefore be called
_Bot__collector_empty_processto be effective. And actually, this should just be called_collector_empty_processThe text was updated successfully, but these errors were encountered: