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

Guozhang Wang commented on KAFKA-7190:
--------------------------------------

Hello [~lambdaliu], before you start picking up this ticket, I still want to 
make sure we have agreed on a solution to resolve this. As I mentioned in the 
email thread:

{code}
We can, probably, improve this situation either in broker side or streams 
client side: on broker side, we can consider delaying the deletion of the 
producer ID for a while; on streams client side, we can consider purging in a 
bit conservative manner (but it is still a bit tricky, since multiple producers 
may be sending to the same inner topic, so just leaving the last N messages to 
not be purged may not be safe still).
{code}

Personally I'd be agree with [~mjsax] that a fix on the broker side may be 
cleaner than having streams client side fix.

> 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)

Reply via email to