# Output isolator pattern not working as expected when elastic is not reachable **URL:** \ **Category:** Logstash\ **Created:** [February 6, 2025, 8:38am UTC](https://discuss.elastic.co/t/output-isolator-pattern-not-working-as-expected-when-elastic-is-not-reachable/374166 "2025-02-06T08:38:53Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [February 6, 2025, 12:14pm UTC](https://discuss.elastic.co/t/output-isolator-pattern-not-working-as-expected-when-elastic-is-not-reachable/374166/2 "2025-02-06T12:14:30Z")
Hello and welcome, > [@himans](#): > > Now when the connectivity of elastic is lost, it doesn't push events to http and mongodb also. This is expected, the output isolator pattern can be a little misleading sometimes, as a blocked output can still block the other inputs. In your case your first pipeline has an output that sends to 3 other pipelines using the pipeline-to-pipeline communicaton. One of those pipelines has an Elasticsearch output, so if this output is not working, the logstash memory queue will start to fill up and once it is full it stops accepting new events, this will then propagate to the first pipeline, which will tell the beats input to backoff, this will affect all other outputs in this pipeline. One alternative would be to use some udp input/output that would drop the evens instead of blocking it, but this also may not be what you want. This example is described in this [similar post](https://discuss.elastic.co/t/logstash-multiple-pipelines-failure-with-persistent-queues/296520/2). --- _[View the full topic](https://discuss.elastic.co/t/output-isolator-pattern-not-working-as-expected-when-elastic-is-not-reachable/374166)._