zeppelin报错master is set as yarn, but spark.submit.deployMode is not specified

具体报错如下:

java.lang.RuntimeException: master is set as yarn, but spark.submit.deployMode is not specifiedat org.apache.zeppelin.interpreter.launcher.SparkInterpreterLauncher.getDeployMode(SparkInterpreterLauncher.java:345)at org.apache.zeppelin.interpreter.launcher.SparkInterpreterLauncher.buildEnvFromProperties(SparkInterpreterLauncher.java:76)at org.apache.zeppelin.interpreter.launcher.StandardInterpreterLauncher.launch(StandardInterpreterLauncher.java:87)at org.apache.zeppelin.interpreter.InterpreterSetting.createInterpreterProcess(InterpreterSetting.java:847)at org.apache.zeppelin.interpreter.ManagedInterpreterGroup.getOrCreateInterpreterProcess(ManagedInterpreterGroup.java:63)at org.apache.zeppelin.interpreter.remote.RemoteInterpreter.getOrCreateInterpreterProcess(RemoteInterpreter.java:110)at org.apache.zeppelin.interpreter.remote.RemoteInterpreter.internal_create(RemoteInterpreter.java:163)at org.apache.zeppelin.interpreter.remote.RemoteInterpreter.open(RemoteInterpreter.java:131)at org.apache.zeppelin.interpreter.remote.RemoteInterpreter.getFormType(RemoteInterpreter.java:298)at org.apache.zeppelin.notebook.Paragraph.jobRun(Paragraph.java:431)at org.apache.zeppelin.notebook.Paragraph.jobRun(Paragraph.java:74)at org.apache.zeppelin.scheduler.Job.run(Job.java:172)at org.apache.zeppelin.scheduler.AbstractScheduler.runJob(AbstractScheduler.java:130)at org.apache.zeppelin.scheduler.RemoteScheduler$JobRunner.run(RemoteScheduler.java:159)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:748)

解决方案:

export MASTER=yarn

改成:

export MASTER=yarn-client

然后重启zeppelin

zeppelin报错master is set as yarn, but spark.submit.deployMode is not specified相关推荐

spark Spare pi 测试报错 master address 设置
搭建好spark 环境之后,按照网上说的用IdeaIl 运行,会报错 Exception in thread "main" org.apache.spark.SparkExcept ...
hive sql 报错后继续执行_Hive优化之Spark执行引擎参数调优（二）
Hive是大数据领域常用的组件之一,主要是大数据离线数仓的运算,关于Hive的性能调优在日常工作和面试中是经常涉及的的一个点,因此掌握一些Hive调优是必不可少的一项技能.影响Hive效率的主要有数据 ...
CentOS 7.1 Bridge启用STP报错Master connection not found or invalid
今天在公司测试Linux bridge搭建,为了使内部docker容器的网络能够不经过2层封装转发对外公布,顾试用一下bridge功能,结果碰到报错:"Bringing up interfa ...
zeppelin报错jdk版本低
报错信息 org.apache.zeppelin.interpreter.InterpreterException: java.io.IOException: Fail to launch inter ...
【Flink】Flink yarn 下报错ClassNotFoundException: org.apache.hadoop.yarn.api.ApplicationConstants$Environ
1.概述 flink启动日志报错如下 2020-08-28 16:44:19,839 ERROR org.apache.flink.client.cli
解决hbase报错Master exiting
使用版本: hadoop-2.10.1 hbase-2.4.15 执行命令start-hbase.sh后主进程Hmaster和从进程HRegionServer都没有启动.查看日志报错如下: 可以看到具 ...
Spark 中 JVM 内存使用及配置详情、spark报错与调优、Spark内存溢出OOM异常
一般在我们开发spark程序的时候,从代码开发到上线以及后期的维护中,在整个过程中都需要涉及到调优的问题,即一开始需要考虑如何把代码写的更简洁高效调优(即代码优化),待开发测试完成后,提交任务时综合考 ...
hbase启动的时候报错java.lang.ClassNotFoundException: org.slf4j.LoggerFactory
启动hbase的时候报错: master running as process 15806. Stop it first. Desktop: regionserver running as proce ...
使用npm下载包，报错 error An unexpected error occurred: “EPERM: operation not permitted
先用了 npm Install 安装相关依赖,后用 yarn 方式来安装依赖,在用yarn安装的时候遇到下图报错信息方式一首次使用 npm 安装依赖报错的问题,造成 yarn 访问依赖文件夹出错, ...

zeppelin报错master is set as yarn, but spark.submit.deployMode is not specified

zeppelin报错master is set as yarn, but spark.submit.deployMode is not specified相关推荐

最新文章

热门文章