# Handling failures with Logstash

**URL:** <https://discuss.elastic.co/t/handling-failures-with-logstash/174854>\
**Category:** Logstash\
**Created:** [April 1, 2019, 7:09pm UTC](https://discuss.elastic.co/t/handling-failures-with-logstash/174854 "2019-04-01T19:09:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ed.sam13](https://avatars.discourse-cdn.com/v4/letter/e/eb8c5e/32.png) [@ed.sam13](https://discuss.elastic.co/u/ed.sam13)\
**Post date:** [April 1, 2019, 7:09pm UTC](https://discuss.elastic.co/t/handling-failures-with-logstash/174854/1 "2019-04-01T19:09:12Z")

</div>

We have a logstash pipeline with JDBC input and Elastic search output.

If the log stash pipeline is scheduled to pick deltas every 15 mins and in 15 mins there are 1000 updates, what happens if the logstash pipeline fails in the 7th minute after processing 400 records. If it is restarted does it start from delta #1 or from delta #401? During our tests we found that it starts at delta #1. Is there a way to avoid this?

---

<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:** [April 29, 2019, 7:09pm UTC](https://discuss.elastic.co/t/handling-failures-with-logstash/174854/2 "2019-04-29T19:09:17Z")

</div>

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