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 2018/07/23 16:44:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16553095#comment-16553095 ]
Matthias J. Sax commented on KAFKA-7190:
----------------------------------------
Thanks for picking this up [~lambdaliu].
I would like to get [~hachikuji] input on this, as I am not sure if it might make sense to fix this issue broker side and keep the PID longer, even if all data from topic was deleted. Not sure how hard this would be, but it might be cleaner, instead of "messing around" on the client layer.
If we agree to fix it on the client layer, we might want to discuss how to fix it if you have a proposal for a fix, [~lambdaliu].
> 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: lambdaliu
> Priority: Major
>
> 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)