Filebeat connecting to a ES cluster that is removed from config file

Elastic Stack Beats
1

Hi,

I had previously configured filebeat to connect to 2 ES hosts in filebeat.yml. I have modified the config file to

output.elasticsearch.hosts: ["es02.net:443"]
#output.elasticsearch.hosts: ["es01.net:443", "es02.net:443"]

Both are running version 8.8.0.

However, in my filebeat log, I still see the messages

"log.origin":{"file.name":"eslegclient/connection.go","file.line":108},"message":"elasticsearch url: es02.net:443","service.name":"filebeat","ecs.version":"1.6.0"
"log.origin":{"file.name":"eslegclient/connection.go","file.line":108},"message":"elasticsearch url: es01.net:443","service.name":"filebeat","ecs.version":"1.6.0"
... <each repeated 8 times, might be because I have configured output.elasticsearch.worker: 8>

and
"log.origin":{"file.name":"pipeline/client_worker.go","file.line":148},"message":"Connecting to backoff(failover(monitoring(es01.net:443),monitoring(es01.net:443),monitoring(es01.net:443),monitoring(es01.net:443),monitoring(es01.net:443),monitoring(es01.net:443),monitoring(es01.net:443),monitoring(es01.net:443),monitoring(es02.net:443),monitoring(es02.net:443),monitoring(es02.net:443),monitoring(es02.net:443),monitoring(es02.net:443),monitoring(es02.net:443),monitoring(es02.net:443),monitoring(es02.net:443))),""service.name":"filebeat","ecs.version":"1.6.0"

Since I have already removed es01.net:443, why is filebeat still trying to connect to it? Is there some other configuration I have missed?

Thank you.

2

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.