You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Jacques Nadeau (JIRA)" <ji...@apache.org> on 2014/06/09 09:17:05 UTC
[jira] [Updated] (DRILL-785)
org.apache.drill.exec.rpc.bit.ListenerPool leak suspects
[ https://issues.apache.org/jira/browse/DRILL-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacques Nadeau updated DRILL-785:
---------------------------------
Component/s: (was: Execution - Flow)
Execution - RPC
Assignee: Jacques Nadeau
> org.apache.drill.exec.rpc.bit.ListenerPool leak suspects
> --------------------------------------------------------
>
> Key: DRILL-785
> URL: https://issues.apache.org/jira/browse/DRILL-785
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - RPC
> Affects Versions: 1.0.0-milestone-1
> Reporter: griffin li
> Assignee: Jacques Nadeau
> Priority: Critical
> Attachments: memoryleak.jpg
>
>
> the drillbit down for every 7 or 8 day. i print the gc details and find a lot of full gc before down. I dump the heap and analysis with mat and find the ListenerPool may have problem.
> Below is the full message in mat leak suspects:
> One instance of "org.apache.drill.exec.rpc.bit.ListenerPool" loaded by "sun.misc.Launcher$AppClassLoader @ 0x638052d50" occupies 3,484,931,208 (98.72%) bytes. The memory is accumulated in one instance of "java.util.concurrent.ConcurrentHashMap$Segment[]" loaded by "<system class loader>".
> Keywords
> java.util.concurrent.ConcurrentHashMap$Segment[]
> org.apache.drill.exec.rpc.bit.ListenerPool
> sun.misc.Launcher$AppClassLoader @ 0x638052d50
> Then i quick look at ListenerPool and does not find any place to remove object from the listeners. Does this is a problem?
--
This message was sent by Atlassian JIRA
(v6.2#6252)