Github user skonto commented on the issue:
https://github.com/apache/spark/pull/20641
@krcz yes it should be ok. So I verified it:
Dispatcher passes the following command to mesos:
```18/06/13 10:30:45 INFO MesosClusterScheduler: Command for the driver
(test):./bin/spark-submit --name test --master
mesos://zk://master.mesos:2181/mesos --driver-cores 1.0 --driver-memory 1000M
--class org.apache.spark.examples.SparkPi --conf
spark.executor.extraJavaOptions="-Dexecutor.test.param1=\"value 1\"
-Dexecutor.test.param2=value\\ 2 -Dexecutor.test.path=\$PATH" --conf
spark.mesos.containerizer=mesos --conf spark.driver.supervise=false --conf
spark.app.name=test --conf spark.driver.memory=1000M --conf
```
spark-class will run this at the executor side:
```
exec /usr/lib/jvm/jre1.8.0_152/bin/java -cp
'/opt/spark/dist/conf/:/opt/spark/dist/jars/*:/etc/hadoop/'
'-Dexecutor.test.param1=value 1' '-Dexecutor.test.param2=value 2'
'-Dexecutor.test.path=$PATH' -Xmx1024m
org.apache.spark.executor.CoarseGrainedExecutorBackend --driver-url
spark://[email protected]:33887
--executor-id 9 --hostname 10.0.0.77 --cores 3 --app-id
bddf96ce-45f6-45f7-ac83-5a3622cafc41-0032-driver-20180613103044-0001
```
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
