[
https://issues.apache.org/jira/browse/KAFKA-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15000651#comment-15000651
]
Luke Steensen commented on KAFKA-2805:
--------------------------------------
[~mgharat] To answer your question from the mailing list, I was only running
one broker in the cluster for this case. My intention was to do a simple test
of the new behavior before pushing the new version to one of our deployed
environments.
It's worth noting that you can get this same behavior with the following
producer config:
{code}
retries=0
max.block.ms=1000
{code}
I will continue testing, but it does seem that the configs are respected when
running more than one broker.
Thanks for taking a look!
Luke
> RecordAccumulator request timeout not enforced when all brokers are gone
> ------------------------------------------------------------------------
>
> Key: KAFKA-2805
> URL: https://issues.apache.org/jira/browse/KAFKA-2805
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Assignee: Mayuresh Gharat
> Fix For: 0.9.0.0
>
>
> When no brokers are left in the cluster, the producer seems not to enforce
> the request timeout as expected.
> From the user mailing list, the null check in batch expiration in
> RecordAccumulator seems questionable:
> https://github.com/apache/kafka/blob/ae5a5d7c08bb634576a414f6f2864c5b8a7e58a3/clients/src/main/java/org/apache/kafka/clients/producer/internals/RecordAccumulator.java#L220.
>
> If this is correct behavior, it is probably worthwhile clarifying the purpose
> of the check in a comment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
