Description
The code path to handle this exists only for the coarse grained mode, and even in this mode the java options aren't passed to the executors properly. We currently pass the entire value of spark.executor.extraJavaOptions to the executors as a string without splitting it. We need to use Utils.splitCommandString as in standalone mode.
I have not confirmed this, but I would assume spark.executor.extraClassPath and spark.executor.extraLibraryPath are also not propagated correctly in either mode.
Attachments
Issue Links
- duplicates
-
SPARK-2608 Mesos doesn't handle spark.executor.extraJavaOptions correctly (among other things)
-
- Resolved
-