# Kafka Input read from beginning after reboot

**URL:** <https://discuss.elastic.co/t/kafka-input-read-from-beginning-after-reboot/130399>\
**Category:** Logstash\
**Created:** [May 3, 2018, 8:27am UTC](https://discuss.elastic.co/t/kafka-input-read-from-beginning-after-reboot/130399 "2018-05-03T08:27:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohanRask](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/johanrask/32/22713_2.png) [@JohanRask](https://discuss.elastic.co/u/JohanRask)\
**Post date:** [May 3, 2018, 8:27am UTC](https://discuss.elastic.co/t/kafka-input-read-from-beginning-after-reboot/130399/1 "2018-05-03T08:27:09Z")

</div>

Hi,  
we are running logstash-6.1.3 with kafka 1.1 in a test environment. Two logstash instances and four brokers.

Yesterday after all machines where suddenly restarted (yes, in test this happens), everything first looked fine **but then we saw that when logstash was started, it had read everything from beginning from all topics instead of the latest offset.**

I can see in our config that same group and client id´s are used and kafka-consumer-groups show that the same consumer-group + client-id is used in kafka.

Note that this error occured on logstash only, we are using kafka-connect as well without this problem.

I understand that this is a longshot, but any input is appreciated.

Regards /Johan

---

<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:** [May 31, 2018, 8:27am UTC](https://discuss.elastic.co/t/kafka-input-read-from-beginning-after-reboot/130399/2 "2018-05-31T08:27:14Z")

</div>

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