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 2019/06/12 18:25:01 UTC
[jira] [Reopened] (KAFKA-7190) Under low traffic conditions purging
repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID
[ https://issues.apache.org/jira/browse/KAFKA-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guozhang Wang reopened KAFKA-7190:
----------------------------------
Assignee: Guozhang Wang (was: lambdaliu)
Reopening this issue since broker would immediately cleanup producer ID upon "incrementing the starting offset" logically, even if the physical log segments have not been garbage collected yet. It means that KIP-443 would not help resolving this issue.
> Under low traffic conditions purging repartition topics cause WARN statements about UNKNOWN_PRODUCER_ID
> ---------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-7190
> URL: https://issues.apache.org/jira/browse/KAFKA-7190
> Project: Kafka
> Issue Type: Improvement
> Components: core, streams
> Affects Versions: 1.1.0, 1.1.1
> Reporter: Bill Bejeck
> Assignee: Guozhang Wang
> Priority: Major
> Fix For: 2.3.0
>
>
> When a streams application has little traffic, then it is possible that consumer purging would delete
> even the last message sent by a producer (i.e., all the messages sent by
> this producer have been consumed and committed), and as a result, the broker
> would delete that producer's ID. The next time when this producer tries to
> send, it will get this UNKNOWN_PRODUCER_ID error code, but in this case,
> this error is retriable: the producer would just get a new producer id and
> retries, and then this time it will succeed.
>
> Possible fixes could be on the broker side, i.e., delaying the deletion of the produderIDs for a more extended period or on the streams side developing a more conservative approach to deleting offsets from repartition topics
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)