You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Matthias J. Sax (JIRA)" <ji...@apache.org> on 2019/02/17 18:46:00 UTC

[jira] [Commented] (KAFKA-7747) Consumer should check for truncation after leader changes

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

Matthias J. Sax commented on KAFKA-7747:
----------------------------------------

Moving all major/minor/trivial tickets that are not merged yet out of 2.2 release.

> Consumer should check for truncation after leader changes
> ---------------------------------------------------------
>
>                 Key: KAFKA-7747
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7747
>             Project: Kafka
>          Issue Type: Improvement
>          Components: consumer
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Major
>
> The change is documented in KIP-320: https://cwiki.apache.org/confluence/display/KAFKA/KIP-320%3A+Allow+fetchers+to+detect+and+handle+log+truncation. After a leader change, the consumer needs to verify its current fetch offset



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)