# Kafka - Commit offset only after batch has been processed
**URL:** https://discuss.elastic.co/t/kafka-commit-offset-only-after-batch-has-been-processed/120445
**Category:** Logstash
**Created:** [February 19, 2018, 12:14pm UTC](https://discuss.elastic.co/t/kafka-commit-offset-only-after-batch-has-been-processed/120445 "2018-02-19T12:14:46Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@shaharmor](https://discuss.elastic.co/u/shaharmor)
#### Post date: [February 19, 2018, 12:14pm UTC](https://discuss.elastic.co/t/kafka-commit-offset-only-after-batch-has-been-processed/120445/1 "2018-02-19T12:14:46Z")
Hey,
I understand after reading the code of the logstash-input-kafka plugin, that the offset it being committed after the batch has been transferred to the logstash internal queue, but not actually sent to the output (In my case Elasticsearch output).
Is there a wait to force logstash to wait for the batch to be fully committed to Elasticsearch before committing the offset to Kafka?
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [February 19, 2018, 12:20pm UTC](https://discuss.elastic.co/t/kafka-commit-offset-only-after-batch-has-been-processed/120445/2 "2018-02-19T12:20:57Z")
This is currently not possible, but there is an [open issue](https://github.com/elastic/logstash/issues/8514) covering discussions around this type of functionality.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 19, 2018, 12:21pm UTC](https://discuss.elastic.co/t/kafka-commit-offset-only-after-batch-has-been-processed/120445/3 "2018-03-19T12:21:05Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.