[
https://issues.apache.org/jira/browse/DRILL-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286825#comment-14286825
]
Daniel Barclay (Drill/MapR) commented on DRILL-1866:
----------------------------------------------------
Yes, the problem (a race condition somewhere in canceling queries and/or
fragments and updating state) still seems to exist.
(My in-progress change for DRILL-1735 (a big chain starting with closing JDBC
connections) includes a workaround change to two tests to suppress the
race-condition failures.
Trying a version with that workaround removed seems to show the same symptom
(child allocators not closed by the time a top-level allocator is closed).)
> Tests that include limit sporadically fail when run as part of entire test
> suite on Linux
> -----------------------------------------------------------------------------------------
>
> Key: DRILL-1866
> URL: https://issues.apache.org/jira/browse/DRILL-1866
> Project: Apache Drill
> Issue Type: Bug
> Components: Tools, Build & Test
> Reporter: Jacques Nadeau
> Assignee: Daniel Barclay (Drill/MapR)
> Priority: Critical
> Fix For: 0.8.0
>
>
> Seems to be a timing issue where memory is not being released as part of
> limit cancellation of a query.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
