[
https://issues.apache.org/jira/browse/DRILL-6838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16683302#comment-16683302
]
weijie.tong commented on DRILL-6838:
------------------------------------
[~aravi5] I have reproduced the error and fixed that at the latest commit. The
actual reason is the close sequence of memory resource at the
FragmentContextImpl close method. The runtime filter should be closed before
the allocator closing.
Another enhancement is to release the runtime filter one more time if it
arrived at the probe side fragment context, but finally not consumed by the
RuntimeFilterRecordBatch.
> Query with Runtime Filter fails with IllegalStateException: Memory was leaked
> by query
> --------------------------------------------------------------------------------------
>
> Key: DRILL-6838
> URL: https://issues.apache.org/jira/browse/DRILL-6838
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
> Affects Versions: 1.15.0
> Environment: Drill 1.15 + PR ->
> [https://github.com/apache/drill/pull/1504]
> Reporter: Abhishek Ravi
> Assignee: weijie.tong
> Priority: Major
> Fix For: 1.15.0
>
> Attachments: RuntimeFilterMemoryLeak.log
>
>
> When running *TPC-H* queries with Runtime Filter feature enabled on DRILL
> 1.15.0 SNAPSHOT, I saw failures with following error:
> {noformat}
> Error: SYSTEM ERROR: IllegalStateException: Memory was leaked by query.
> Memory leaked: (1048576)
> Allocator(frag:5:38) 6000000/1048576/77833920/50062914560
> (res/actual/peak/limit)
> Fragment 5:38
> Please, refer to logs for more information.
> [Error Id: 2ca07049-ac92-4944-929c-16f261e43f7e on qa-node185.qa.lab:31010]
> (state=,code=0)
> {noformat}
> The failure is observed when the query has nested joins. (TPC-H query 7 can
> easily reproduce the issue). I have attached logs for a simpler sample query
> that fails.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
