Open vkakhnych opened 4 years ago
UPD: No any additional listener in the system:
[root@batch01 ~]# netstat -natp | grep 504[4-9]
tcp 0 0 127.0.0.1:5044 0.0.0.0:* LISTEN 17190/ruby
tcp 0 0 127.0.0.1:43746 127.0.0.1:5044 ESTABLISHED 17773/filebeat
tcp 1452155 0 127.0.0.1:5044 127.0.0.1:43746 ESTABLISHED 17190/ruby
Ok, I might misunderstood multi workers approach. Get it worked after adjusting config:
<system>
workers 4
</system>
<worker 0>
<source>
@type beats
bind 127.0.0.1
</source>
</worker>
<worker 1>
<source>
@type beats
bind 127.0.0.1
</source>
</worker>
<worker 2>
<source>
@type beats
bind 127.0.0.1
</source>
</worker>
<worker 3>
<source>
@type beats
bind 127.0.0.1
</source>
</worker>
And added these hosts/ports to filebeat config accordingly.
We have a simple config:
But running top I see load on the only one worker. It hits 100% CPU consuming and we're loosing logs.
Amazon Linux ver. 1,