# \[2.1.3\] Regarding Outputs to Multiple ES Clusters

**URL:** <https://discuss.elastic.co/t/2-1-3-regarding-outputs-to-multiple-es-clusters/50408>\
**Category:** Logstash\
**Created:** [May 19, 2016, 7:08am UTC](https://discuss.elastic.co/t/2-1-3-regarding-outputs-to-multiple-es-clusters/50408 "2016-05-19T07:08:11Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [May 19, 2016, 7:08am UTC](https://discuss.elastic.co/t/2-1-3-regarding-outputs-to-multiple-es-clusters/50408/1 "2016-05-19T07:08:11Z")

</div>

Hi,  
Atm, most of our traffic is hitting logstash via the beats input. We output to two clusters, one of which is significantly bigger than the other. And periodically, we see congestion reported by beats and it backs off.

My questions is, given this behaviour, do we need to split the output definition for our second elasticsearch cluster to a separate logstash instance? The idea being to avoid issues with one cluster impacting ingestion to the other...

Regards,  
David

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [May 19, 2016, 7:11am UTC](https://discuss.elastic.co/t/2-1-3-regarding-outputs-to-multiple-es-clusters/50408/2 "2016-05-19T07:11:56Z")

</div>

Logstash currently has a single event pipeline, so if you want to make outputs independent of each other you need two instances.

---

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [May 19, 2016, 9:03am UTC](https://discuss.elastic.co/t/2-1-3-regarding-outputs-to-multiple-es-clusters/50408/3 "2016-05-19T09:03:08Z")

</div>

What version will we need to go to for this not to be an issue?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [May 19, 2016, 9:34am UTC](https://discuss.elastic.co/t/2-1-3-regarding-outputs-to-multiple-es-clusters/50408/4 "2016-05-19T09:34:45Z")

</div>

No currently released Logstash has support for multiple pipelines. I'm not sure it's even planned. Or am I misunderstanding the question?

---

<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:** [May 19, 2016, 12:28pm UTC](https://discuss.elastic.co/t/2-1-3-regarding-outputs-to-multiple-es-clusters/50408/5 "2016-05-19T12:28:49Z")

</div>

You're correct.

---

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [May 19, 2016, 1:14pm UTC](https://discuss.elastic.co/t/2-1-3-regarding-outputs-to-multiple-es-clusters/50408/6 "2016-05-19T13:14:32Z")

</div>

Ok, thanks for clearing this up.

---

<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:** [July 6, 2017, 4:56am UTC](https://discuss.elastic.co/t/2-1-3-regarding-outputs-to-multiple-es-clusters/50408/7 "2017-07-06T04:56:57Z")

</div>