Prabhjyot Singh created ZEPPELIN-5197:
-----------------------------------------

             Summary: Livy.sql interpreter fails to execute
                 Key: ZEPPELIN-5197
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5197
             Project: Zeppelin
          Issue Type: Bug
          Components: livy-interpreter
            Reporter: Prabhjyot Singh
            Assignee: Prabhjyot Singh


If `zeppelin.livy.concurrentSQL` is set to false then livy-interpreter fails 
with following exception:


{code:java}
java.lang.RuntimeException: Fail to callRemoteFunction, because connection is 
broken
        at 
org.apache.zeppelin.interpreter.remote.PooledRemoteClient.callRemoteFunction(PooledRemoteClient.java:108)
        at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterProcess.callRemoteFunction(RemoteInterpreterProcess.java:98)
        at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreter.interpret(RemoteInterpreter.java:208)
        at org.apache.zeppelin.notebook.Paragraph.jobRun(Paragraph.java:490)
        at org.apache.zeppelin.notebook.Paragraph.jobRun(Paragraph.java:72)
        at org.apache.zeppelin.scheduler.Job.run(Job.java:172)
        at 
org.apache.zeppelin.scheduler.AbstractScheduler.runJob(AbstractScheduler.java:132)
        at 
org.apache.zeppelin.scheduler.RemoteScheduler$JobRunner.run(RemoteScheduler.java:182)
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
{code}




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to