You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Shantanu Deshmukh (JIRA)" <ji...@apache.org> on 2018/09/19 12:44:00 UTC

[jira] [Commented] (KAFKA-4493) Connections to Kafka brokers should be validated

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

Shantanu Deshmukh commented on KAFKA-4493:
------------------------------------------

We are using Kafka 0.10.1.0 and our Kafka producers are consuming huge amount of memory. Heapdump analysis showed almost 1 GB memory consumed by *org.apache.kafka.common.network.Selector* and *org.apache.kafka.common.network.KafkaChannel*.

 

Can I apply this patch for Kafka 0.10.1.0? Sorry, but I don't know much about GIT and patching process. Please guide.

> Connections to Kafka brokers should be validated
> ------------------------------------------------
>
>                 Key: KAFKA-4493
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4493
>             Project: Kafka
>          Issue Type: Improvement
>          Components: clients
>            Reporter: Ismael Juma
>            Priority: Major
>
> There have been a few reports of Kafka clients throwing an OOM because they read 4 bytes from the stream and then use that to allocate a ByteBuffer without validating that they are using the right security protocol or even communicating with a Kafka broker.
> It would be good to perform some validation in order to show a useful error message to the user instead of the OOM.



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