You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2017/02/03 17:01:51 UTC
[jira] [Commented] (KAFKA-4725) Kafka broker fails due to OOM when
producer exceeds throttling quota for extended periods of time
[ https://issues.apache.org/jira/browse/KAFKA-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15851730#comment-15851730 ]
Ismael Juma commented on KAFKA-4725:
------------------------------------
Nice catch, a contribution via a PR would be welcome indeed.
> Kafka broker fails due to OOM when producer exceeds throttling quota for extended periods of time
> -------------------------------------------------------------------------------------------------
>
> Key: KAFKA-4725
> URL: https://issues.apache.org/jira/browse/KAFKA-4725
> Project: Kafka
> Issue Type: Bug
> Components: core, producer
> Affects Versions: 0.10.1.1
> Environment: Ubuntu Trusty (14.04.5), Oracle JDK 8
> Reporter: Jeff Chao
> Priority: Critical
> Labels: reliability
> Fix For: 0.10.3.0, 0.10.2.1
>
> Attachments: oom-references.png
>
>
> Steps to Reproduce:
> 1. Create a non-compacted topic with 1 partition
> 2. Set a produce quota of 512 KB/s
> 3. Send messages at 20 MB/s
> 4. Observe heap memory growth as time progresses
> Investigation:
> While running performance tests with a user configured with a produce quota, we found that the lead broker serving the requests would exhaust heap memory if the producer sustained a inbound request throughput greater than the produce quota.
> Upon further investigation, we took a heap dump from that broker process and discovered the ThrottledResponse object has a indirect reference to the byte[] holding the messages associated with the ProduceRequest.
> We're happy contributing a patch but in the meantime wanted to first raise the issue and get feedback from the community.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)