You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Gary Russell (Jira)" <ji...@apache.org> on 2020/11/05 15:35:00 UTC

[jira] [Commented] (KAFKA-10683) Consumer.position() Ignores Transaction Marker with read_uncommitted

    [ https://issues.apache.org/jira/browse/KAFKA-10683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17226774#comment-17226774 ] 

Gary Russell commented on KAFKA-10683:
--------------------------------------

In addition, position() does not take the marker into account when {noformat}max.poll.records=1{noformat}

> Consumer.position() Ignores Transaction Marker with read_uncommitted
> --------------------------------------------------------------------
>
>                 Key: KAFKA-10683
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10683
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients, core
>    Affects Versions: 2.6.0
>            Reporter: Gary Russell
>            Priority: Minor
>
> The workaround for https://issues.apache.org/jira/browse/KAFKA-6607# Says:
> {quote}
> or use `consumer.position()` that takes the commit marker into account and would "step over it")
> {quote}
> Note that this problem occurs with all consumers, not just Streams. We have implemented this solution in our project (as an option for those users concerned about the pseudo lag).
> We have discovered that this technique will only work with {code}isolation.level=read_committed{code} Otherwise, the {code}position(){code} call does not include the marker "record".
> https://github.com/spring-projects/spring-kafka/issues/1587#issuecomment-721899560



--
This message was sent by Atlassian Jira
(v8.3.4#803005)