You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Colin P. McCabe (JIRA)" <ji...@apache.org> on 2017/04/26 21:58:04 UTC
[jira] [Resolved] (KAFKA-4958) kafka.server.KafkaServerStartable -
java.lang.OutOfMemoryError: Java heap space
[ https://issues.apache.org/jira/browse/KAFKA-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colin P. McCabe resolved KAFKA-4958.
------------------------------------
Resolution: Not A Problem
Correct me if I'm wrong, but this doesn't seem like a bug. New versions of Kafka may use more or less memory than previous versions.
From the stack overflow page, it appears that you configured {{log.cleaner.dedupe.buffer.size}} to a smaller size to use less memory. You could also have increased Java heap size.
> kafka.server.KafkaServerStartable - java.lang.OutOfMemoryError: Java heap space
> -------------------------------------------------------------------------------
>
> Key: KAFKA-4958
> URL: https://issues.apache.org/jira/browse/KAFKA-4958
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.10.2.0
> Reporter: Karthik
>
> I upgraded to storm 1.0.3 and along with it, I am using kafka 0.10.2.0 to start mock kafka instances. I am getting heap space errors with all 0.10.x.x versions where as 0.8.x.x version works fine. For further information, please look at http://stackoverflow.com/questions/43050796/kafka-server-kafkaserverstartable-java-lang-outofmemoryerror-java-heap-space
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)