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/05/17 13:41:05 UTC

[jira] [Updated] (KAFKA-5250) handleFetchRequest should do down conversion after throttling

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

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

> handleFetchRequest should do down conversion after throttling
> -------------------------------------------------------------
>
>                 Key: KAFKA-5250
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5250
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Ismael Juma
>            Assignee: Rajini Sivaram
>            Priority: Critical
>             Fix For: 0.11.0.0
>
>
> We currently do down conversion before throttling. This is good from the perspective of getting the correct message size, but it means that we can cause OOMs due to excessive memory retention. That is, by performing down conversion, we are loading the records into the heap even though we are not ready to send them yet.
> It would be preferable to throttle before down conversion.
> In addition, we currently updates bytesOut before throttling. We should do it after throttling as well.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)