You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by "Jeff Zhang (JIRA)" <ji...@apache.org> on 2016/08/02 01:00:35 UTC
[jira] [Created] (ZEPPELIN-1263) Should specify zeppelin's spark
configuration through --conf arguments of spark-submit
Jeff Zhang created ZEPPELIN-1263:
------------------------------------
Summary: Should specify zeppelin's spark configuration through --conf arguments of spark-submit
Key: ZEPPELIN-1263
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1263
Project: Zeppelin
Issue Type: Bug
Affects Versions: 0.6.0
Reporter: Jeff Zhang
Assignee: Jeff Zhang
For now, we load zeppelin's spark configuration at runtime in the RemoteInterpreter Process rather than loading them before starting the process (through --conf of spark-submit). It is fine for most of spark configuration, but for some configuration, it would introduce some weird issues. Like ZEPPELIN-1242, and if you specify spark.master as yarn-client in spark-defaults.conf but specify spark.master as local in zeppelin side, you will see the spark interpreter fail to start due to this inconsistency.
So I propose to specify zeppelin's spark configuration through --conf arguments of spark-submit
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)