# Logstash pipeline blocks every write if one index isn't available

**URL:** <https://discuss.elastic.co/t/logstash-pipeline-blocks-every-write-if-one-index-isnt-available/236151>\
**Category:** Logstash\
**Created:** [June 8, 2020, 10:02am UTC](https://discuss.elastic.co/t/logstash-pipeline-blocks-every-write-if-one-index-isnt-available/236151 "2020-06-08T10:02:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![YvorL](https://avatars.discourse-cdn.com/v4/letter/y/9fc348/32.png) [@YvorL](https://discuss.elastic.co/u/YvorL)\
**Post date:** [June 8, 2020, 10:02am UTC](https://discuss.elastic.co/t/logstash-pipeline-blocks-every-write-if-one-index-isnt-available/236151/1 "2020-06-08T10:02:13Z")

</div>

Hi,

My issue is that when I receive an event with a timestamp that's in the past, which would be written to the previous date-based index, it'll be blocked due to frozen state. However, that prevents every other event (the majority) from indexing too. I lost millions of current events during the weekend because there were some old ones that couldn't be indexed. While I obviously need to weed out the root issue, I'm wondering how I can avoid this issue.  
Is there any way to redirect events that are "too old" to process the normal way to a "dummy" index? Or any other scenario where I still can freeze my old indices?

Thank you!

---

<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 6, 2020, 10:02am UTC](https://discuss.elastic.co/t/logstash-pipeline-blocks-every-write-if-one-index-isnt-available/236151/2 "2020-07-06T10:02:15Z")

</div>

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