You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Dhruvil Shah (JIRA)" <ji...@apache.org> on 2018/05/21 21:08:00 UTC

[jira] [Commented] (KAFKA-6927) Broker uses significant amount of memory during down-conversion

    [ https://issues.apache.org/jira/browse/KAFKA-6927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483063#comment-16483063 ] 

Dhruvil Shah commented on KAFKA-6927:
-------------------------------------

[https://github.com/apache/kafka/pull/4871]

> Broker uses significant amount of memory during down-conversion
> ---------------------------------------------------------------
>
>                 Key: KAFKA-6927
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6927
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>            Reporter: Dhruvil Shah
>            Assignee: Dhruvil Shah
>            Priority: Major
>             Fix For: 2.0.0
>
>
> Kafka broker could consume significant amount of memory when down-conversion is required. We have seen scenarios where this causes out of memory errors. This issue and the proposed fix is described in detail in KIP-283 - [https://cwiki.apache.org/confluence/display/KAFKA/KIP-283%3A+Efficient+Memory+Usage+for+Down-Conversion]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)