[
https://issues.apache.org/jira/browse/KAFKA-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034882#comment-17034882
]
ASF GitHub Bot commented on KAFKA-6607:
---------------------------------------
mjsax commented on pull request #8091: KAFKA-6607: Commit correct offsets for
transactional input data
URL: https://github.com/apache/kafka/pull/8091
Port of #8040 to `trunk` -- the only real difference is the missing check of
we are in pending shutdown and a task is not found -- in `trunk` we always
create all new task hence this check is not necessary.
\cc @guozhangwang
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Consumer Client and Kafka Streams lag not zero when input topic transactional
> -----------------------------------------------------------------------------
>
> Key: KAFKA-6607
> URL: https://issues.apache.org/jira/browse/KAFKA-6607
> Project: Kafka
> Issue Type: Improvement
> Components: clients, streams
> Affects Versions: 1.0.0
> Reporter: Matthias J. Sax
> Assignee: Matthias J. Sax
> Priority: Minor
>
> When an input topic for a Consumer or Kafka Streams application is written
> using transaction, the client does not commit "endOffset" but "endOffset - 1"
> (or to be more precise, "lastProcessedMessageOffset + 1") if it reaches the
> end of topic. The reason is the commit marker that is the last "message" in
> the topic; Streams commit "offset of last processed message plus 1" and does
> not take commit markers into account.
> This is not a correctness issue, but when one inspect the consumer lag via
> {{bin/kafka-consumer.group.sh}} the lag is show as 1 instead of 0 – what is
> correct from consumer-group tool point of view.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
