[jira] [Commented] (DRILL-2510) Unclosed allocators detected in Java shutdown hook

["Chris Westin (JIRA)" <ji...@apache.org>]

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

Chris Westin commented on DRILL-2510:
-------------------------------------

Since the problems were in "mvn install" tests, I didn't run the precommit suite before submitting the review. I'm running it now just to be sure, in case we want to wait for that.

> Unclosed allocators detected in Java shutdown hook
> --------------------------------------------------
>
>                 Key: DRILL-2510
>                 URL: https://issues.apache.org/jira/browse/DRILL-2510
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Flow
>    Affects Versions: 0.7.0
>            Reporter: Chris Westin
>            Assignee: Jacques Nadeau
>             Fix For: 0.8.0
>
>         Attachments: DRILL-2510.1.patch.txt
>
>
> We're seeing errors in logs that look like this:
> {code}
> Exception in thread "Drillbit-ShutdownHook#1" 
> java.lang.IllegalStateException: Failure while trying to close allocator: Child level allocators not closed. Stack trace:
>                 java.lang.Thread.getStackTrace(Thread.java:1589)
>                 org.apache.drill.exec.memory.TopLevelAllocator.getChildAllocator(TopLevelAllocator.java:126)
>                 org.apache.drill.exec.ops.FragmentContext.<init>(FragmentContext.java:111)
>                 org.apache.drill.exec.work.foreman.Foreman.setupRootFragment(Foreman.java:763)
>                 org.apache.drill.exec.work.foreman.Foreman.runPhysicalPlan(Foreman.java:349)
>                 org.apache.drill.exec.work.foreman.Foreman.runSQL(Foreman.java:737)
>                 org.apache.drill.exec.work.foreman.Foreman.run(Foreman.java:202)
>                 org.apache.drill.common.SelfCleaningRunnable.run(SelfCleaningRunnable.java:38)
>                 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>                 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>                 java.lang.Thread.run(Thread.java:745)
>         at org.apache.drill.exec.memory.TopLevelAllocator.close(TopLevelAllocator.java:159)
>         at org.apache.drill.exec.server.BootStrapContext.close(BootStrapContext.java:75)
>         at com.google.common.io.Closeables.close(Closeables.java:77)
>         at com.google.common.io.Closeables.closeQuietly(Closeables.java:108)
>         at org.apache.drill.exec.server.Drillbit.close(Drillbit.java:267)
>         at org.apache.drill.exec.server.Drillbit$ShutdownThread.run(Drillbit.java:285)
> {code}
> This might be a result of sharing the jvm across test classes during mvn install runs, but it might also be a new problem, because some examples can be seen in individual tests run from IDEs.
> Investigate.



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