Supreeth Sharma created ZEPPELIN-3418:
-----------------------------------------
Summary: User need to be informed if path to the provided jar file
is incorrect
Key: ZEPPELIN-3418
URL: https://issues.apache.org/jira/browse/ZEPPELIN-3418
Project: Zeppelin
Issue Type: Bug
Components: zeppelin-server
Affects Versions: 0.8.0
Reporter: Supreeth Sharma
Fix For: 0.8.0
The user need to be informed if path to the provided jar file is incorrect.
Steps to reproduce :
Step 1: Create para1 as below:
{code:java}
%spark2.conf
spark.jars /tmp/spark2-examples-assembly-2.3.0.3.0.0.0-1145.jar
spark.app.name per_user_hrt_1_1livy2
{code}
where '/tmp/spark2-examples-assembly-2.3.0.3.0.0.0-1145.jar' is incorect
Step 2: Run para2 as below
{code:java}
%spark2
sc.version
{code}
If user provides incorrect jar file path, then first para which creates the
config("%spark2.conf") runs fine without providing any errors or warnings.
Now when the user tries to run subsequent para, then it fails with very generic
message as below and it doesn't provide any information for user to know that
the failure is due to bad configuration.
{code}
java.lang.NullPointerException at
org.apache.zeppelin.spark.Utils.invokeMethod(Utils.java:44) at
org.apache.zeppelin.spark.Utils.invokeMethod(Utils.java:39) at
org.apache.zeppelin.spark.OldSparkInterpreter.createSparkContext_2(OldSparkInterpreter.java:375)
at
org.apache.zeppelin.spark.OldSparkInterpreter.createSparkContext(OldSparkInterpreter.java:364)
at
org.apache.zeppelin.spark.OldSparkInterpreter.getSparkContext(OldSparkInterpreter.java:172)
at
org.apache.zeppelin.spark.OldSparkInterpreter.open(OldSparkInterpreter.java:740)
at org.apache.zeppelin.spark.SparkInterpreter.open(SparkInterpreter.java:61)
at
org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:69)
at
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:617)
at org.apache.zeppelin.scheduler.Job.run(Job.java:186) at
org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:139) 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}
Same issue exists for livy2 sessions as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
