# Logstash multi-pipeline output failure breaks other pipelines

**URL:** <https://discuss.elastic.co/t/logstash-multi-pipeline-output-failure-breaks-other-pipelines/243246>\
**Category:** Logstash\
**Created:** [July 30, 2020, 3:47pm UTC](https://discuss.elastic.co/t/logstash-multi-pipeline-output-failure-breaks-other-pipelines/243246 "2020-07-30T15:47:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dave\_Waters](https://avatars.discourse-cdn.com/v4/letter/d/e68b1a/32.png) [@Dave\_Waters](https://discuss.elastic.co/u/Dave_Waters)\
**Post date:** [July 30, 2020, 3:47pm UTC](https://discuss.elastic.co/t/logstash-multi-pipeline-output-failure-breaks-other-pipelines/243246/1 "2020-07-30T15:47:34Z")

</div>

Running Logstash 7.8.1

Multi pipelines

Pipeline A output to B and C  
B output to ES cluster 1  
C output to ES cluster 2

Shutdown ES cluster 1  
Error from output attempt to send bulk request... normal error when ES is down

However, I would expect A -\> C to still flow, but it does not, the entire flow is now stalled.

Is this expected? I thought the pipelines worked independently?

Thanks.

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [July 30, 2020, 5:16pm UTC](https://discuss.elastic.co/t/logstash-multi-pipeline-output-failure-breaks-other-pipelines/243246/2 "2020-07-30T17:16:30Z")

</div>

> [@Dave\_Waters](#):
>
> Is this expected?

No, that is the whole point of the [output isolator](https://www.elastic.co/guide/en/logstash/current/pipeline-to-pipeline.html#output-isolator-pattern) pattern. Are you using persistent queues? The in-memory queues may back up enough to cause the pipeline to block.

---

<div class="post-metadata">

**Author:** ![Dave\_Waters](https://avatars.discourse-cdn.com/v4/letter/d/e68b1a/32.png) [@Dave\_Waters](https://discuss.elastic.co/u/Dave_Waters)\
**Post date:** [July 30, 2020, 6:15pm UTC](https://discuss.elastic.co/t/logstash-multi-pipeline-output-failure-breaks-other-pipelines/243246/3 "2020-07-30T18:15:15Z")

</div>

Yes - we use in memory queues. Persistent queues don’t scale well when spread across a large cluster dropping files to disk everywhere.

I feel like this is a bug?

---

<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:** [August 27, 2020, 6:15pm UTC](https://discuss.elastic.co/t/logstash-multi-pipeline-output-failure-breaks-other-pipelines/243246/4 "2020-08-27T18:15:21Z")

</div>

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