drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Victoria Markman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-4236) ExternalSort should use the new allocator functionality to better manage it's memory usage
Date Thu, 14 Jan 2016 17:31:39 GMT

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

Victoria Markman commented on DRILL-4236:
-----------------------------------------

I agree that it's a separate bug and I was combing jira to find existing bug, because it's
always been the case that sort could run out of memory in some specific conditions.
Is this something we are going to fix for 1.5.0  and hold release for ? 

> ExternalSort should use the new allocator functionality to better manage it's memory
usage
> ------------------------------------------------------------------------------------------
>
>                 Key: DRILL-4236
>                 URL: https://issues.apache.org/jira/browse/DRILL-4236
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Execution - Relational Operators
>    Affects Versions: 1.5.0
>            Reporter: Deneche A. Hakim
>            Assignee: Deneche A. Hakim
>              Labels: documentation
>             Fix For: 1.5.0
>
>
> Before DRILL-4215, the sort operator wasn't able to correctly compute it's memory usage,
and so it jumped through a bunch of hoops to try to figure out when it should spill to disk.
> With the transfer accounting in place, this code can be greatly simplified to just use
the current operator memory allocation.



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

Mime
View raw message