storm-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Radim Kolar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (STORM-387) Memory leak in worker
Date Fri, 04 Jul 2014 09:31:37 GMT

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

Radim Kolar commented on STORM-387:
-----------------------------------

symptoms of this problem are exactly same as in this discussion. Root of problem is not in
zookeeper<->worker communication, as you can see from discussion raising timeouts did
not helped, JVM is just stuck with running GC all the time, having no resources to communicate
with zookeeper.

http://mail-archives.apache.org/mod_mbox/storm-user/201405.mbox/%3CBAY179-W879A8BC16B2EFB02ED8334933E0@phx.gbl%3E

> Memory leak in worker
> ---------------------
>
>                 Key: STORM-387
>                 URL: https://issues.apache.org/jira/browse/STORM-387
>             Project: Apache Storm (Incubating)
>          Issue Type: Bug
>    Affects Versions: 0.9.2-incubating
>         Environment: FreeBSD 10/i386
>            Reporter: Radim Kolar
>              Labels: leak, qa
>
> There is memory leak in worker. I can reproduce it every time with following code: 
> https://github.com/hsn10/stormtest
> worker running bolt 'rtt' only leaks memory. Deploy topology and leave it about 15 minutes
running until worker is killed by supervisor due to heartbeat timeout. It timeouts because
its busy running gc all the time as you can see in jconsole.
> I was able to do memory dump, but due to its size jhat tool was not able to load it in
reasonable time (i killed it after 30 minutes)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message