Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
0.7.0
-
None
Description
A user reported at MapR Answers Forum that SQLLine hangs and the Drillbit log contains the following error
2014-12-30 20:34:03,060 [WorkManager-1] ERROR o.apache.drill.exec.work.WorkManager - Failure while running wrapper [Foreman: 2b5cf3c7-7705-4a18-3457-2d80f9800eb6] java.lang.NullPointerException: null at org.apache.drill.exec.work.foreman.Foreman.cancelExecutingFragments(Foreman.java:483) ~[drill-java-exec-0.7.0-SNAPSHOT-rebuffed.jar:0.7.0-SNAPSHOT] at org.apache.drill.exec.work.foreman.Foreman.moveToState(Foreman.java:436) ~[drill-java-exec-0.7.0-SNAPSHOT-rebuffed.jar:0.7.0-SNAPSHOT] at org.apache.drill.exec.work.foreman.Foreman.run(Foreman.java:194) ~[drill-java-exec-0.7.0-SNAPSHOT-rebuffed.jar:0.7.0-SNAPSHOT] at org.apache.drill.exec.work.WorkManager$RunnableWrapper.run(WorkManager.java:254) ~[drill-java-exec-0.7.0-SNAPSHOT-rebuffed.jar:0.7.0-SNAPSHOT] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_71] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_71] at java.lang.Thread.run(Thread.java:745) [na:1.7.0_71]
This happens if the JDK compiler can not be created during query execution, which results in org.apache.drill.exec.work.foreman.Foreman.rootRunner not getting initialized.
Attachments
Attachments
Issue Links
- is duplicated by
-
DRILL-1918 Drill does very obscure things when a JRE is used instead of a JDK.
- Resolved