You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "Hanifi Gunes (JIRA)" <ji...@apache.org> on 2014/10/29 00:01:33 UTC

[jira] [Resolved] (DRILL-1519) Concurrent access to WorkEventBus#getOrCreateFragmentManager leaks memory.

     [ https://issues.apache.org/jira/browse/DRILL-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hanifi Gunes resolved DRILL-1519.
---------------------------------
    Resolution: Duplicate

> Concurrent access to WorkEventBus#getOrCreateFragmentManager leaks memory.
> --------------------------------------------------------------------------
>
>                 Key: DRILL-1519
>                 URL: https://issues.apache.org/jira/browse/DRILL-1519
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Hanifi Gunes
>            Assignee: DrillCommitter
>
> WorkEventBus uses a ConcurrentHashMap to ensure there is one and only one FragmentManager corresponding to each unique FragmentHandle. The method creates a FragmentManager that reserves some initial memory if a thread observes that it is not in the map. However, in case of concurrent access, we still need to clean up after if multiple threads observe that FragmentManager does not exist and create multiple FragmentManagers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)