[
https://issues.apache.org/jira/browse/KAFKA-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679625#comment-13679625
]
Senthil Chittibabu commented on KAFKA-936:
------------------------------------------
The application ramps up within few minutes to consume the message from the
queue, I understand if the metrics memory grows during the ramp up, but
shouldn't it remain flat after that. But I see the Metrics instance grow
steadily.
I did noticed the kafka_2.8.0-0.8.0-SNAPSHOT downgraded the metrics jars from
3.0 to 2.2.0. I did not have this issue with initial version of kafka 0.8 with
metrics_core_3.0.0. Is there any reason this was done?
Anyway, I will increase the maxPermSize to 1g or 2g from 512m and run the test
again.
> Kafka Metrics Memory Leak
> --------------------------
>
> Key: KAFKA-936
> URL: https://issues.apache.org/jira/browse/KAFKA-936
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Affects Versions: 0.8
> Environment: centos linux, jdk 1.6, jboss
> Reporter: Senthil Chittibabu
> Assignee: Neha Narkhede
> Priority: Critical
>
> I am using kafka_2.8.0-0.8.0-SNAPSHOT version. I am running into
> OutOfMemoryError in PermGen Space. I have set the -XX:MaxPermSize=512m, but I
> still get the same error. I used profiler to trace the memory leak, and found
> the following kafka classes to be the cause for the memory leak. Please let
> me know if you need any additional information to debug this issue.
> kafka.server.FetcherLagMetrics
> kafka.consumer.FetchRequestAndResponseMetrics
> kafka.consumer.FetchRequestAndResponseStats
> kafka.metrics.KafkaTimer
> kafka.utils.Pool
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
