# How not to keep track of commit offset with kafka

**URL:** <https://discuss.elastic.co/t/how-not-to-keep-track-of-commit-offset-with-kafka/160423>\
**Category:** Logstash\
**Created:** [December 11, 2018, 5:58pm UTC](https://discuss.elastic.co/t/how-not-to-keep-track-of-commit-offset-with-kafka/160423 "2018-12-11T17:58:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gunbird1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gunbird1/32/29619_2.png) [@gunbird1](https://discuss.elastic.co/u/gunbird1)\
**Post date:** [December 11, 2018, 5:58pm UTC](https://discuss.elastic.co/t/how-not-to-keep-track-of-commit-offset-with-kafka/160423/1 "2018-12-11T17:58:36Z")

</div>

Hi,

I'm doing mostly testing on a logstash that consumes events from kafka.

I frequently stop the logstash and can restart it several hours or days later.

I don't want to keep track of the event offset because when I restart logstash after a long period of stop, I collect old events from 2 days ago.

What is the configuration for the kafka input plugin to restart with the latest event in the queue ?

Rhanks for your help.

---

<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:** [January 8, 2019, 5:58pm UTC](https://discuss.elastic.co/t/how-not-to-keep-track-of-commit-offset-with-kafka/160423/2 "2019-01-08T17:58:55Z")

</div>

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