[
https://issues.apache.org/jira/browse/KAFKA-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681233#comment-13681233
]
Senthil Chittibabu commented on KAFKA-936:
------------------------------------------
Yes, I see lot of rebalances (can't rebalance after 4 retries) in the log.. And
also I see the below the warning often. Not sure is there any relation with
memory leak?
2013-06-11 23:59:59,861 WARN
[kafka.consumer.ConsumerFetcherManager$LeaderFinderThread]
(UrlWorker-grp_hms.com-1370985065479-bb5e7de1-leader-finder-thread], Failed to
find leader for Set([dev--raw-topic,10], [ption
at org.I0Itec.zkclient.ZkClient$2.call(ZkClient.java:416)
[zkclient-0.2.jar:0.2]
at org.I0Itec.zkclient.ZkClient$2.call(ZkClient.java:413)
[zkclient-0.2.jar:0.2]
at org.I0Itec.zkclient.ZkClient.retryUntilConnected(ZkClient.java:675)
[zkclient-0.2.jar:0.2]
at org.I0Itec.zkclient.ZkClient.getChildren(ZkClient.java:413)
[zkclient-0.2.jar:0.2]
at org.I0Itec.zkclient.ZkClient.getChildren(ZkClient.java:409)
[zkclient-0.2.jar:0.2]
at kafka.utils.ZkUtils$.getChildrenParentMayNotExist(ZkUtils.scala:438)
[kafka_2.8.0-0.8.0-SNAPSHOT.jar:0.8.0
at kafka.utils.ZkUtils$.getAllBrokersInCluster(ZkUtils.scala:75)
[kafka_2.8.0-0.8.0-SNAPSHOT.jar:0.8.0-SNAPSH
at
kafka.consumer.ConsumerFetcherManager$LeaderFinderThread.doWork(ConsumerFetcherManager.scala:62)
[kafka_2.
at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51)
[kafka_2.8.0-0.8.0-SNAPSHOT.jar:0.8.0-SNAP
> 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
