[jira] [Updated] (KAFKA-4725) Kafka broker fails due to OOM when producer exceeds throttling quota for extended periods of time

2017-02-07 Thread Jun Rao (JIRA)

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

Jun Rao updated KAFKA-4725:
---
   Resolution: Fixed
Fix Version/s: (was: 0.10.3.0)
   Status: Resolved  (was: Patch Available)

Issue resolved by pull request 2496
[https://github.com/apache/kafka/pull/2496]

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


[jira] [Updated] (KAFKA-4725) Kafka broker fails due to OOM when producer exceeds throttling quota for extended periods of time

2017-02-06 Thread Ewen Cheslack-Postava (JIRA)

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

Ewen Cheslack-Postava updated KAFKA-4725:
-
Reviewer: Jun Rao
  Status: Patch Available  (was: Open)

> 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.2.0, 0.10.3.0
>
> 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)


[jira] [Updated] (KAFKA-4725) Kafka broker fails due to OOM when producer exceeds throttling quota for extended periods of time

2017-02-06 Thread Ewen Cheslack-Postava (JIRA)

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

Ewen Cheslack-Postava updated KAFKA-4725:
-
Fix Version/s: (was: 0.10.2.1)
   0.10.2.0

> 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.2.0, 0.10.3.0
>
> 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)


[jira] [Updated] (KAFKA-4725) Kafka broker fails due to OOM when producer exceeds throttling quota for extended periods of time

2017-02-03 Thread Ismael Juma (JIRA)

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

Ismael Juma updated KAFKA-4725:
---
Fix Version/s: 0.10.3.0

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


[jira] [Updated] (KAFKA-4725) Kafka broker fails due to OOM when producer exceeds throttling quota for extended periods of time

2017-02-03 Thread Ismael Juma (JIRA)

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

Ismael Juma updated KAFKA-4725:
---
Priority: Critical  (was: Major)

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


[jira] [Updated] (KAFKA-4725) Kafka broker fails due to OOM when producer exceeds throttling quota for extended periods of time

2017-02-03 Thread Ismael Juma (JIRA)

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

Ismael Juma updated KAFKA-4725:
---
Fix Version/s: 0.10.2.1

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


[jira] [Updated] (KAFKA-4725) Kafka broker fails due to OOM when producer exceeds throttling quota for extended periods of time

2017-02-03 Thread Ismael Juma (JIRA)

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

Ismael Juma updated KAFKA-4725:
---
Labels: reliability  (was: )

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