Closed makefu closed 6 years ago
I can confirm this behavior, as it's the reason I stopped using this plugin. It's most likely the underlying ruby gem Cinch, over which we have no control. I haven't taken the time to investigate alternatives, or to troubleshoot this in any other way.
🤔 This code looks like it could be problematic; whenever the queue is empty, we immediately try again, with no backoff:
while !stop? begin msg = @irc_queue.pop(true) handle_response(msg, output_queue) rescue ThreadError # Empty queue end end
thanks!
For some reason the logstash irc input plugin runs at 100% cpu load even though nothing happens.
filter { }
output { stdout { codec => rubydebug } }
bin/logstash -w 1 --log.level warn -f