drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacques Nadeau (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:58:39 GMT

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

Jacques Nadeau commented on DRILL-4236:
---------------------------------------

I guess it depends on how much more frequent the problems are. Do you have a sense of this?
I think this is structural and has existed for some time so my first inclination is that it
is not a release blocker. That said, if, even with the config changes, this is substantially
more frequent, we should probably take stock. 

> 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