[
https://issues.apache.org/jira/browse/KAFKA-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624873#comment-14624873
]
Parth Brahmbhatt commented on KAFKA-1788:
-----------------------------------------
[~becket_qin] So is this jira irrelavant at this point? If yes can I resolve
it? If no, can you describe what needs to be done? I know you had a KIP and
multiple discussions but I am not sure if you are taking of it as part of
KAFKA-2142. I will be happy to continue working on this jira if you can
describe what needs to be done.
> 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.0
> Reporter: Jun Rao
> Assignee: Parth Brahmbhatt
> Labels: newbie++
> Fix For: 0.8.3
>
> Attachments: KAFKA-1788.patch, KAFKA-1788_2015-01-06_13:42:37.patch,
> KAFKA-1788_2015-01-06_13:44:41.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)
