Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4188#issuecomment-73334927
@vanzin the code in `ExecutorRunnable.scala` that handles the executor opts
still does build up `javaOpts` as a collection. You're saying it doesn't need
this treatment because that `List[String]` goes straight to `setCommands` in
the YARN API? The thing is, it is exactly `spark.executor.extraJavaOpts` that
was the problem, so I imagine something has to change. You made an additional
comment that YARN actually won't escape these arguments, so we should? this
makes me dizzy.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
