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

**URL:** <https://discuss.elastic.co/t/filebeat-connecting-to-a-es-cluster-that-is-removed-from-config-file/352238>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [February 1, 2024, 1:46am UTC](https://discuss.elastic.co/t/filebeat-connecting-to-a-es-cluster-that-is-removed-from-config-file/352238 "2024-02-01T01:46:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hjazz6](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hjazz6/32/79007_2.png) [@hjazz6](https://discuss.elastic.co/u/hjazz6)\
**Post date:** [February 1, 2024, 1:46am UTC](https://discuss.elastic.co/t/filebeat-connecting-to-a-es-cluster-that-is-removed-from-config-file/352238/1 "2024-02-01T01:46:27Z")

</div>

Hi,

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

```auto
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

```auto
"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.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 29, 2024, 3:47am UTC](https://discuss.elastic.co/t/filebeat-connecting-to-a-es-cluster-that-is-removed-from-config-file/352238/2 "2024-02-29T03:47:23Z")

</div>

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