[
https://issues.apache.org/jira/browse/DRILL-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083061#comment-16083061
]
Paul Rogers commented on DRILL-5265:
------------------------------------
There are no logs or profiles attached to this issue.
In general, Drill's allocator mechanism will kill a query that attempts to
allocate more memory than the limit. The sort does "fudge" by giving itself an
extra 10% margin, but should (almost) never use it.
This is, perhaps, an error with rounding? MiB vs. MB units confusion? Can't
tell until I see the profile and logs...
> External Sort consumes more memory than allocated
> -------------------------------------------------
>
> Key: DRILL-5265
> URL: https://issues.apache.org/jira/browse/DRILL-5265
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Rahul Challapalli
> Fix For: 1.12.0
>
>
> git.commit.id.abbrev=300e934
> Based on the profile for the below query, the external sort has a peak memory
> usage of ~126MB when only ~100MB was allocated
> {code}
> alter session set `planner.memory.max_query_memory_per_node` = 104857600;
> alter session set `planner.width.max_per_node` = 1;
> select * from dfs.`/drill/testdata/md1362` order by c_email_address;
> {code}
> I attached the profile and the log files
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
