# Does one failed output kill / stop the whole pipeline?

**URL:** <https://discuss.elastic.co/t/does-one-failed-output-kill-stop-the-whole-pipeline/182209>\
**Category:** Logstash\
**Created:** [May 22, 2019, 11:02am UTC](https://discuss.elastic.co/t/does-one-failed-output-kill-stop-the-whole-pipeline/182209 "2019-05-22T11:02:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![bjosve](https://avatars.discourse-cdn.com/v4/letter/b/ecae2f/32.png) [@bjosve](https://discuss.elastic.co/u/bjosve)\
**Post date:** [May 22, 2019, 11:02am UTC](https://discuss.elastic.co/t/does-one-failed-output-kill-stop-the-whole-pipeline/182209/1 "2019-05-22T11:02:50Z")

</div>

Hi,

I have a logstash output like this,

> output {  
> tcp {  
> mode =\> "client"  
> host =\> "server01"  
> port =\> 5400  
> codec =\> "line"  
> }  
> tcp {  
> mode =\> "client"  
> host =\> "server02"  
> port =\> 5400  
> codec =\> "line"  
> }  
> file {  
> path =\> "/logs/%{[filename]}-%{+YYYY.MM.dd}"  
> write\_behavior =\> "append"  
> file\_mode =\> 0600  
> }  
> elasticsearch {  
> hosts =\> ["[http://server3:9200](http://server3:9200)"]  
> index =\> "%{[logtype]}-%{+YYYY.MM.dd}"  
> }  
> }

It seems as if one output fails, the whole pipeline stops? If, for example, a tcp output fails, it will retry about 20 times, then everything stops. Is this default behavior? and if so, is there any way around it?

Best Regards,  
Bjorn

---

<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:** [May 22, 2019, 12:09pm UTC](https://discuss.elastic.co/t/does-one-failed-output-kill-stop-the-whole-pipeline/182209/2 "2019-05-22T12:09:41Z")

</div>

If an output cannot write events then it will queue them. If the queue fills then back-pressure will shut down the pipeline. That is working as expected.

---

<div class="post-metadata">

**Author:** ![bjosve](https://avatars.discourse-cdn.com/v4/letter/b/ecae2f/32.png) [@bjosve](https://discuss.elastic.co/u/bjosve)\
**Post date:** [May 22, 2019, 2:25pm UTC](https://discuss.elastic.co/t/does-one-failed-output-kill-stop-the-whole-pipeline/182209/3 "2019-05-22T14:25:45Z")

</div>

Thanks Badger

> That is working as expected.

That seems logical, but will it stop to process all outputs if one fail? Let's say that output#1#2 works and #3 fails. Will it stop at this output and retry it until it works again and never reach output#4?

Thanks again.

/Bjorn

---

<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:** [May 22, 2019, 8:09pm UTC](https://discuss.elastic.co/t/does-one-failed-output-kill-stop-the-whole-pipeline/182209/4 "2019-05-22T20:09:53Z")

</div>

Yes, there is a limited amount of queue space. Once that is filled processing will stop.

---

<div class="post-metadata">

**Author:** ![bjosve](https://avatars.discourse-cdn.com/v4/letter/b/ecae2f/32.png) [@bjosve](https://discuss.elastic.co/u/bjosve)\
**Post date:** [May 24, 2019, 1:35pm UTC](https://discuss.elastic.co/t/does-one-failed-output-kill-stop-the-whole-pipeline/182209/5 "2019-05-24T13:35:34Z")

</div>

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:** [June 21, 2019, 1:35pm UTC](https://discuss.elastic.co/t/does-one-failed-output-kill-stop-the-whole-pipeline/182209/6 "2019-06-21T13:35:44Z")

</div>

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