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 2015/02/15 19:18:11 UTC

[jira] [Commented] (DRILL-2252) Cancelling a fragment is not cleaning up RecordBatches

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

Hanifi Gunes commented on DRILL-2252:
-------------------------------------

-1 (non-binding). There is a corner case here that may cause clean-up been called more than once, which should fail. Please verify & fix if concern is legitimate.

> Cancelling a fragment is not cleaning up RecordBatches
> ------------------------------------------------------
>
>                 Key: DRILL-2252
>                 URL: https://issues.apache.org/jira/browse/DRILL-2252
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Flow
>            Reporter: Venki Korukanti
>            Assignee: Venki Korukanti
>         Attachments: DRILL-2252-1.patch
>
>
> Currently FragmentExecutor exits out of processing loop once a fragment is cancelled, but it is not cleaning up the operators. This causes some operators to leak resources. For example ScanBatch closes the currently open files as part of the cleanup, because of this bug now it leaves some open files.
> To repro:
> Run a query that involves LIMIT in loop and observe the memory used by the Drillbit go up consistently. 



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