[
https://issues.apache.org/jira/browse/KAFKA-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14261356#comment-14261356
]
Bhavesh Mistry commented on KAFKA-1788:
---------------------------------------
[~parth.brahmbhatt],
The close() (#2) issue will be address by the jira ticket
https://issues.apache.org/jira/browse/KAFKA-1788, but still following will not
be address when leader is available, but no records can be sent. [~junrao],
[~jkreps] and [~nehanarkhede], please let me know correct behavior in case of
above use case. should I file another issue ?
1) record-error-rate metric remain zero despite firewall rule. In my opinion,
it should have called org.apache.kafka.clients.producer.Callback but I did not
see that happening either one or two are brokers not reachable.
Thanks,
Bhavesh
> producer record can stay in RecordAccumulator forever if leader is no
> available
> -------------------------------------------------------------------------------
>
> Key: KAFKA-1788
> URL: https://issues.apache.org/jira/browse/KAFKA-1788
> Project: Kafka
> Issue Type: Bug
> Components: core, producer
> Affects Versions: 0.8.2
> Reporter: Jun Rao
> Assignee: Jun Rao
> Labels: newbie++
> Fix For: 0.8.3
>
> Attachments: KAFKA-1788.patch
>
>
> In the new producer, when a partition has no leader for a long time (e.g.,
> all replicas are down), the records for that partition will stay in the
> RecordAccumulator until the leader is available. This may cause the
> bufferpool to be full and the callback for the produced message to block for
> a long time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
