[
https://issues.apache.org/jira/browse/KAFKA-17541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18035575#comment-18035575
]
Apoorv Mittal commented on KAFKA-17541:
---------------------------------------
Hi [~isding_l], will it be possible for you to pick the case 2 now, we have
merged KIP-1206 changes now. In case you do not have bandwidth then please let
me know and I can pick it up.
> Improve handling of delivery count
> ----------------------------------
>
> Key: KAFKA-17541
> URL: https://issues.apache.org/jira/browse/KAFKA-17541
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Andrew Schofield
> Assignee: Lan Ding
> Priority: Major
> Fix For: 4.2.0
>
>
> There are two situations in which the delivery count handling needs to be
> more intelligent.
> First, for records which are automatically released as a result of closing a
> share session normally, the delivery count should not be incremented. These
> records were fetched but they were not actually delivered to the client since
> the disposition of the delivery records is carried in the ShareAcknowledge
> which closes the share session. Any remaining records were not delivered,
> only fetched.
> Second, for records which have a delivery count which is more than 1 or 2,
> there is a suspicion that the records are not being delivered due to a
> problem rather than just natural retrying. The batching of these records
> should be reduced, even down to a single record as a time so we do not have
> the failure to deliver a poisoned record actually causing adjacent records to
> be considered unsuccessful and potentially reach the delivery count limit
> without proper reason.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
