# Logstash Pipeline Sequence
**URL:** https://discuss.elastic.co/t/logstash-pipeline-sequence/62114
**Category:** Logstash
**Created:** [October 3, 2016, 11:37pm UTC](https://discuss.elastic.co/t/logstash-pipeline-sequence/62114 "2016-10-03T23:37:57Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@chromechris](https://discuss.elastic.co/u/chromechris)
#### Post date: [October 3, 2016, 11:37pm UTC](https://discuss.elastic.co/t/logstash-pipeline-sequence/62114/1 "2016-10-03T23:37:57Z")
Hello Loggers,
I am wondering what happens when a Logstash thread get stuck at the input/filter-output level. Does Logstash create new threads to continue, or does it stay stuck indefinitely. I am asking this because I fed a 3.6 GB doc to Logstash, and I saw funny things happening. It took a while for around 700 message to go trough, then for about 10 minutes nothing else would get through Logstash. I decided to restart it, and about 1000 new messages went though (I believe these came from the SIGTERM flush). The rest of the messages never came through, but I think the rest of the messages did not come through because the when I restarted Logstash, the input threads were cut. Any thoughts?
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [October 5, 2016, 8:17am UTC](https://discuss.elastic.co/t/logstash-pipeline-sequence/62114/2 "2016-10-05T08:17:26Z")
[https://www.elastic.co/guide/en/logstash/current/pipeline.html](https://www.elastic.co/guide/en/logstash/current/pipeline.html) should help.
But if an input blocks then everything blocks as LS doesn't have any state machine internals.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 4:35am UTC](https://discuss.elastic.co/t/logstash-pipeline-sequence/62114/3 "2017-07-06T04:35:44Z")