[ https://issues.apache.org/jira/browse/KAFKA-10688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228844#comment-17228844 ]
Guozhang Wang commented on KAFKA-10688: --------------------------------------- Normally the repartition topic should never have an invalid offset after setting it initially, since the repartition topic's retention should be infinity and we only truncate it via the delete-records; this ticket is for guarding against abnormal cases e.g. if users accidentally truncated the repartition topics. > 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 > Priority: Major > > 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)