[jira] [Updated] (KAFKA-2805) RecordAccumulator request timeout not enforced when all brokers are gone

["Jason Gustafson (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Gustafson updated KAFKA-2805:
-----------------------------------
    Summary: RecordAccumulator request timeout not enforced when all brokers are gone  (was: RecordAccumulator request timeout only enforced if partition leader is unknown)

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