# Logstash Multiple Output Atomicity **URL:** \ **Category:** Logstash\ **Created:** [November 14, 2023, 9:42am UTC](https://discuss.elastic.co/t/logstash-multiple-output-atomicity/347100 "2023-11-14T09:42:57Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![mile3880](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mile3880/32/127544_2.png) [@mile3880](https://discuss.elastic.co/u/mile3880)\ **Post date:** [November 14, 2023, 9:42am UTC](https://discuss.elastic.co/t/logstash-multiple-output-atomicity/347100/1 "2023-11-14T09:42:57Z")
Does Logstash guarantee atomicity of multiple output options? For Example, if I set 2 different outputs to Elasticsearch A and B, and when connection to Elasticsearch A is temporarily unstable, can Logstash stop sending data to ES B or do rollback for sended data to ES A ? ---
**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:** [November 14, 2023, 1:14pm UTC](https://discuss.elastic.co/t/logstash-multiple-output-atomicity/347100/2 "2023-11-14T13:14:48Z")
> [@mile3880](#): > > Does Logstash guarantee atomicity of multiple output options? No, it does not. logstash has an at-least-once delivery model, but that is affected by whether you use [persistent queues](https://www.elastic.co/guide/en/logstash/current/persistent-queues.html), whether restarts or crashes occur and suchlike. It does not support rollback once an event has been sent to an output. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 12, 2023, 1:14pm UTC](https://discuss.elastic.co/t/logstash-multiple-output-atomicity/347100/3 "2023-12-12T13:14:55Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.