You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Deneche A. Hakim (JIRA)" <ji...@apache.org> on 2015/05/05 01:55:06 UTC

[jira] [Updated] (DRILL-2757) Verify operators correctly handle low memory conditions and cancellations

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

Deneche A. Hakim updated DRILL-2757:
------------------------------------
    Attachment: DRILL-2757.1.patch.txt

includes:
DRILL-2893: ScanBatch throws a NullPointerException instead of returning OUT_OF_MEMORY
DRILL-2894: FixedValueVectors shouldn't set it's data buffer to null when it fails to allocate it
DRILL-2895: AbstractRecordBatch.buildSchema() should properly handle OUT_OF_MEMORY outcome
DRILL-2905: RootExec implementations should properly handle IterOutcome.OUT_OF_MEMORY
DRILL-2920: properly handle OutOfMemoryException
DRILL-2947: AllocationHelper.allocateNew() doesn't have a consistent behavior when it can't allocate

also:
- improved how system errors are displayed
- added UserException.memoryError() with a pre assigned error message
- injection site in ScanBatch and unit test that runs various tpch queries and injects an exception in the ScanBatch that will cause an OUT_OF_MEMORY outcome to be sent


> Verify operators correctly handle low memory conditions and cancellations
> -------------------------------------------------------------------------
>
>                 Key: DRILL-2757
>                 URL: https://issues.apache.org/jira/browse/DRILL-2757
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Flow, Execution - Relational Operators
>    Affects Versions: 0.8.0
>            Reporter: Chris Westin
>            Assignee: Deneche A. Hakim
>             Fix For: 1.0.0
>
>         Attachments: DRILL-2757.1.patch.txt
>
>
> Check that the path through sort that notices low memory conditions and causes the sort to spill ("out of memory condition management").
> Also check to make sure we handle queries and fragment failures properly under these conditions.
> "hashjoin, hashagg, and topn use large amounts of memory,and may be unable to
> complete if their memory needs can't be met; for all others, the idea is that they can complete if they get their reservation"



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