[
https://issues.apache.org/jira/browse/KAFKA-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770531#comment-16770531
]
Matthias J. Sax commented on KAFKA-5782:
----------------------------------------
Moving all major/minor/trivial tickets that are not merged yet out of 2.2
release.
> Avoid unnecessary PID reset when expire batches.
> ------------------------------------------------
>
> Key: KAFKA-5782
> URL: https://issues.apache.org/jira/browse/KAFKA-5782
> Project: Kafka
> Issue Type: Improvement
> Components: producer
> Affects Versions: 0.11.0.0
> Reporter: Jiangjie Qin
> Priority: Major
> Fix For: 2.2.0
>
>
> This is more of an efficiency optimization. Currently we will reset PID when
> batch expiration happens and one of the expired batches is in retry mode.
> This is assuming that we don't know if the batch in retry has been appended
> to the broker or not. However, if the batch was in retry due to a retriable
> exception returned by the broker, the batch is not appended. In this case, we
> do not need to reset the PID.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
