drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Rogers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DRILL-5211) Queries fail due to direct memory fragmentation
Date Tue, 06 Jun 2017 19:05:18 GMT

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

Paul Rogers updated DRILL-5211:
    Attachment: EnhancedScanOperator.pdf

Attached a proposal for creating a new, enhanced version of the scan operator that allows
unit tests, uses the revised projection mechanism, and uses the new scan projection mechanism.
This revised version in turn supports retrofitting readers with the size-aware vector writer
by moving most ad-hoc complexity out of the reader into the scan operator.

> Queries fail due to direct memory fragmentation
> -----------------------------------------------
>                 Key: DRILL-5211
>                 URL: https://issues.apache.org/jira/browse/DRILL-5211
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Paul Rogers
>            Assignee: Paul Rogers
>             Fix For: 1.9.0
>         Attachments: ApacheDrillMemoryFragmentationBackground.pdf, ApacheDrillVectorSizeLimits.pdf,
EnhancedScanOperator.pdf, ScanSchemaManagement.pdf
> Consider a test of the external sort as follows:
> * Direct memory: 3GB
> * Input file: 18 GB, with one Varchar column of 8K width
> The sort runs, spilling to disk. Once all data arrives, the sort beings to merge the
results. But, to do that, it must first do an intermediate merge. For example, in this sort,
there are 190 spill files, but only 19 can be merged at a time. (Each merge file contains
128 MB batches, and only 19 can fit in memory, giving a total footprint of 2.5 GB, well below
the 3 GB limit.
> Yet, when loading batch xx, Drill fails with an OOM error. At that point, total available
direct memory is 3,817,865,216. (Obtained from {{maxMemory}} in the {{Bits}} class in the
> It appears that Drill wants to allocate 58,257,868 bytes, but the {{totalCapacity}} (again
in {{Bits}}) is already 3,800,769,206, causing an OOM.
> The problem is that, at this point, the external sort should not ask the system for more
memory. The allocator for the external sort is at just 1,192,350,366 before the allocation
request. Plenty of spare memory should be available, released when the in-memory batches were
spilled to disk prior to merging. Indeed, earlier in the run, the sort had reached a peak
memory usage of 2,710,716,416 bytes. This memory should be available for reuse during merging,
and is plenty sufficient to fill the particular request in question.

This message was sent by Atlassian JIRA

View raw message