[DRILL-1519] Concurrent access to WorkEventBus#getOrCreateFragmentManager leaks memory.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: 0.7.0
• Assignee: DrillCommitter
• Reporter: Hanifi Gunes
• Created: 10/Oct/14 03:06
• Updated: 09/Dec/14 17:47
• Resolved: 28/Oct/14 23:01

Description

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.

Issue Links

• duplicates: DRILL-1504 Enabling fragment memory limit causes out of memory error