# Elasticsearch output hosts list

**URL:** https://discuss.elastic.co/t/elasticsearch-output-hosts-list/248735
**Category:** Logstash
**Created:** [September 15, 2020, 8:21pm UTC](https://discuss.elastic.co/t/elasticsearch-output-hosts-list/248735 "2020-09-15T20:21:52Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![YvorL](https://avatars.discourse-cdn.com/v4/letter/y/9fc348/32.png) [@YvorL](https://discuss.elastic.co/u/YvorL)
#### Post date: [September 15, 2020, 8:21pm UTC](https://discuss.elastic.co/t/elasticsearch-output-hosts-list/248735/1 "2020-09-15T20:21:52Z")

</div>

Hi,

Should I include all Elasticsearch nodes (there are no dedicated masters, and there's one coordinating node) when I specify the list of ES nodes in the output block? I mean in case, I'm horizontally scaling, do I need to update all pipelines on every Logstash node?  
I mean I see that this surely isn't something that'd block anything since I'm not doing it, but maybe there's overhead due to that?

Thank you!

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [September 15, 2020, 9:23pm UTC](https://discuss.elastic.co/t/elasticsearch-output-hosts-list/248735/2 "2020-09-15T21:23:56Z")

</div>

Can you use a DNS CNAME that has all the hosts attached to it?

---

<div class="post-metadata">

### Author: ![YvorL](https://avatars.discourse-cdn.com/v4/letter/y/9fc348/32.png) [@YvorL](https://discuss.elastic.co/u/YvorL)
#### Post date: [September 15, 2020, 11:33pm UTC](https://discuss.elastic.co/t/elasticsearch-output-hosts-list/248735/3 "2020-09-15T23:33:03Z")

</div>

Sorry, I'm not sure how that would be done. I'm not that well versed with DNS.  
Anyway, I don't think that's doable for my case.

Your answer implies a 'yes, you should always append the list', otherwise, your performance will degrade. Am I right?

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [September 15, 2020, 11:34pm UTC](https://discuss.elastic.co/t/elasticsearch-output-hosts-list/248735/4 "2020-09-15T23:34:30Z")

</div>

It depends. If you are talking about hundreds of thousands of events per second, sure. If you're talking about scaling to store data for longer periods, no.

---

<div class="post-metadata">

### Author: ![YvorL](https://avatars.discourse-cdn.com/v4/letter/y/9fc348/32.png) [@YvorL](https://discuss.elastic.co/u/YvorL)
#### Post date: [September 15, 2020, 11:58pm UTC](https://discuss.elastic.co/t/elasticsearch-output-hosts-list/248735/5 "2020-09-15T23:58:36Z")

</div>

There are tens of thousands of events in the LS cluster (for now), ES scaling is somewhat rare, but I like my cluster optimized 🙂

Thanks for your answers!

---

<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: [October 13, 2020, 11:58pm UTC](https://discuss.elastic.co/t/elasticsearch-output-hosts-list/248735/6 "2020-10-13T23:58:48Z")

</div>

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