[jira] [Commented] (DRILL-785) org.apache.drill.exec.rpc.bit.ListenerPool leak suspects

["Aditya Kishore (JIRA)" <ji...@apache.org>]

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

Aditya Kishore commented on DRILL-785:
--------------------------------------

I reproduced this leak while trying to debug the excessive memory use by TestParquetWriter. I am testing the fix now.

> 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: Aditya Kishore
>            Priority: Critical
>             Fix For: 1.0.0-BETA1
>
>         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)