[
https://issues.apache.org/jira/browse/DRILL-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deneche A. Hakim updated DRILL-3147:
------------------------------------
Attachment: DRILL-3147.1.patch.txt
- FragmentContext.close() waits 100ms before closing the allocator to give
enough time to the rpc layer to properly release any batch that was just
transfered to this fragment's allocator
- each time a fragment A sends a "receiver finished" to fragment B, fragment B
id will be added to FragmentContext.ignoredSenders list
- refactored UnorderedReceiverBatch.informSenders() and
MergingRecordBatch.informSenders() by moving this method to FragmentContext
- DataServer.send() uses FragmentContext.ignoredSenders to decide if a batch
should be passed to the fragment or discarded right away
- BaseRawBatchBuffer methods enqueue() and kill() are now synchronized
- TestTpcdsSf1Leak test reproduces the leak, it's ignored by default because it
requires a large dataset
> tpcds-sf1-parquet query 73 causes memory leak
> ---------------------------------------------
>
> Key: DRILL-3147
> URL: https://issues.apache.org/jira/browse/DRILL-3147
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Deneche A. Hakim
> Assignee: Jacques Nadeau
> Fix For: 1.1.0
>
> Attachments: DRILL-3147.1.patch.txt
>
>
> the leak seems to appear when BaseRawBatchBuffer.enqueue() tries to release a
> batch but the allocator has already been closed
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
