# Dead letter queue with multiple outputs

**URL:** <https://discuss.elastic.co/t/dead-letter-queue-with-multiple-outputs/137881>\
**Category:** Logstash\
**Created:** [June 29, 2018, 12:26am UTC](https://discuss.elastic.co/t/dead-letter-queue-with-multiple-outputs/137881 "2018-06-29T00:26:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rocknroll](https://avatars.discourse-cdn.com/v4/letter/r/c6cbf5/32.png) [@rocknroll](https://discuss.elastic.co/u/rocknroll)\
**Post date:** [June 29, 2018, 12:26am UTC](https://discuss.elastic.co/t/dead-letter-queue-with-multiple-outputs/137881/1 "2018-06-29T00:26:42Z")

</div>

Hi there

We have a pipeline with two Elasticsearch outputs, going to separate instances of Elastic - Elastic1 and Elastic2.  
We would like to ensure that if Elastic2 is unavailable, events will still get sent to Elastic1 and we're wondering if defining a dead letter queue would achieve this.

So if Elastic2 is unavailable, will the events get written to Elastic1 **and** the DLQ, or does the Elastic1 event get 'rolled back' and the event only appears on the DLQ?

Many thanks

---

<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 27, 2018, 12:30am UTC](https://discuss.elastic.co/t/dead-letter-queue-with-multiple-outputs/137881/2 "2018-07-27T00:30:40Z")

</div>

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