[
https://issues.apache.org/jira/browse/KAFKA-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193448#comment-15193448
]
Mayuresh Gharat commented on KAFKA-3388:
----------------------------------------
If the batch is retried and re-enqueued, the last append time gets updated and
that is used to time out the batch. So it should not expire immediately.
> Producer should only timeout a batch in the accumulator when metadata is
> missing.
> ---------------------------------------------------------------------------------
>
> Key: KAFKA-3388
> URL: https://issues.apache.org/jira/browse/KAFKA-3388
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.9.0.1
> Reporter: Jiangjie Qin
> Assignee: Jiangjie Qin
> Priority: Blocker
> Fix For: 0.10.0.0
>
>
> In KIP-19 we are reusing the request.timeout.ms to timeout the batches in the
> accumulator. We were intended to avoid the case that the batches sitting in
> the accumulator forever when topic metadata is missing.
> Currently we are not checking if metadata is available or not when we timeout
> the batches in the accumulator (although the comments says we will check the
> metadata). This causes problem that once the previous batch hit a request
> timeout and got retried, all the subsequent batches will fail with timeout
> exception. We should only timeout the batches in the accumulator when the
> metadata of the partition is missing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
