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

Posted to dev@kafka.apache.org by "Guozhang Wang (Jira)" <ji...@apache.org> on 2020/11/05 23:10:00 UTC

[jira] [Created] (KAFKA-10688) Handle accidental truncation of repartition topics as exceptional failure

Guozhang Wang created KAFKA-10688:
-------------------------------------

             Summary: Handle accidental truncation of repartition topics as exceptional failure
                 Key: KAFKA-10688
                 URL: https://issues.apache.org/jira/browse/KAFKA-10688
             Project: Kafka
          Issue Type: Improvement
          Components: streams
            Reporter: Guozhang Wang
            Assignee: Guozhang Wang


Today we always handle InvalidOffsetException from the main consumer by the resetting policy assuming they are for source topics. But repartition topics are also source topics and should never be truncated and hence cause InvalidOffsetException.

We should differentiate these repartition topics from external source topics and treat the InvalidOffsetException from repartition topics as fatal and close the whole application.



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