Github user SherryNJU commented on the issue:
https://github.com/apache/zeppelin/pull/1347
Hiï¼@H4ml3t . **Have you found someway to make Zeppelin 0.6.1 work well
with Spark 2.0.0**, I built both of them using scala 2.11, however, everytime
when I using exeternal spark master, I hit this issue:
{pool-2-thread-2} SparkInterpreter.java[createSparkSession]:334) - Created
Spark session with Hive support
ERROR [2016-09-26 17:08:04,632] ({pool-2-thread-2}
Job.java[run]:182) - Job failed
java.lang.NullPointerException
at
org.apache.zeppelin.spark.SparkInterpreter.open(SparkInterpreter.java:768)
at
org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:69)
at
org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:93)
at
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:341)
at org.apache.zeppelin.scheduler.Job.run(Job.java:176)
at org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:139)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:522)
at java.util.concurrent.FutureTask.run(FutureTask.java:277)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:191)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.lang.Thread.run(Thread.java:785)
INFO [2016-09-26 17:08:04,658] (
{pool-2-thread-2}
SchedulerFactory.java[jobFinished]:137) - Job
remoteInterpretJob_1474880841114 finished by scheduler
org.apache.zeppelin.spark.SparkInterpreter-994533906
ERROR [2016-09-26 17:08:09,775] (
{pool-1-thread-2}
TThreadPoolServer.java[run]:296) - Error occurred during processing of
message.
java.lang.NullPointerException
at
org.apache.zeppelin.spark.SparkInterpreter.open(SparkInterpreter.java:768)
at
org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:69)
at
org.apache.zeppelin.interpreter.LazyOpenInterpreter.getProgress(LazyOpenInterpreter.java:110)
at
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer.getProgress(RemoteInterpreterServer.java:404)
at
org.apache.zeppelin.interpreter.thrift.RemoteInterpreterService$Processor$getProgress.getResult(RemoteInterpreterService.java:1509)
at
org.apache.zeppelin.interpreter.thrift.RemoteInterpreterService$Processor$getProgress.getResult(RemoteInterpreterService.java:1494)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:285)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.lang.Thread.run(Thread.java:785)
**#I know this issue would be solved by Zeppelin 0.6.2, but we are really
running out of time, do we have some workaround way to avoid this, like setting
some additional parameters?**
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
