[
https://issues.apache.org/jira/browse/DRILL-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14509125#comment-14509125
]
Jacques Nadeau commented on DRILL-2847:
---------------------------------------
Further analysis shows that the memory backing these buffers is being released.
Both of these should have been released as well but this isn't really a memory
leak as the java objects will be picked up via GC. Will post a patch shortly
that resolves one of these two pseudo-leaks. Other needs more research.
> DrillBufs from the RPC layer are being leaked
> ---------------------------------------------
>
> Key: DRILL-2847
> URL: https://issues.apache.org/jira/browse/DRILL-2847
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow, Execution - RPC
> Affects Versions: 0.9.0
> Reporter: Chris Westin
> Assignee: Jacques Nadeau
> Fix For: 1.0.0
>
> Attachments: DRILL-2847-bug.2.patch.txt, DRILL-2847-bug.patch.txt,
> drill-mem.log
>
>
> I've created a patch that demonstrates this. In the patch, code is added to
> UnsafeDirectLittleEndian to track all the instances of that class that are
> created (which happens when buffers are allocated inside TopLevelAllocator).
> release() is overridden to remove these from the tracked list when they are
> released. An @After action is added to TestTpchDistributed which checks on
> the count of outstanding buffers. If the test is run, every case fails, and
> each failure shows a progressively larger and larger number of outstanding
> buffers. There are no complaints from the allocator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
