xutao created ZEPPELIN-2882:
-------------------------------

             Summary: Spark Interpreters doesn`t work, report a 
NullPointerException
                 Key: ZEPPELIN-2882
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2882
             Project: Zeppelin
          Issue Type: Bug
    Affects Versions: 0.7.2
         Environment: AWS centos 7
            Reporter: xutao


Hadoop version 2.7.2
Spark version 2.0.0
Zeppelin version 0.7.2

Operation:
1. install the Zeppelin,  and modify  zeppelin-env.sh as following,
export JAVA_HOME=/usr/java/jdk1.8.0_102
export MASTER=spark://hdp-master01:7077
export SPARK_HOME=/usr/local/spark-2.0.0-bin-hadoop2.7
export HADOOP_CONF_DIR=/usr/local/hadoop-2.7.2/etc/hadoop

2. Configure the spark interpreters as following:
master  spark://hdp-master01:7077
spark.app.name  Zeppelin
spark.cores.max 4
spark.executor.memory   4g

3. Open a note ,specify spark as the interpreter, then type 
sc.version

and get  the following result,
java.lang.NullPointerException
        at org.apache.zeppelin.spark.Utils.invokeMethod(Utils.java:38)
        at org.apache.zeppelin.spark.Utils.invokeMethod(Utils.java:33)
        at 
org.apache.zeppelin.spark.SparkInterpreter.createSparkContext_2(SparkInterpreter.java:391)
        at 
org.apache.zeppelin.spark.SparkInterpreter.createSparkContext(SparkInterpreter.java:380)
        at 
org.apache.zeppelin.spark.SparkInterpreter.getSparkContext(SparkInterpreter.java:146)
        at 
org.apache.zeppelin.spark.SparkInterpreter.open(SparkInterpreter.java:828)
        at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:70)
        at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:491)
        at org.apache.zeppelin.scheduler.Job.run(Job.java:175)
        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:1142)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

I really feel wired, and do not know what the problem is, is it a bug ? Anyone 
help me?




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to