Github user zhzhan commented on a diff in the pull request:
https://github.com/apache/spark/pull/3409#discussion_r21139101
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ClientBase.scala ---
@@ -360,6 +360,10 @@ private[spark] trait ClientBase extends Logging {
}
}
+ // include yarn am specific java options
+ sparkConf.getOption("spark.yarn.am.extraJavaOptions")
+ .foreach(opts => javaOpts += opts)
--- End diff --
@andrewor14 I checked the usage of Utils.splitCommandString, and it does
not serve the purpose. Also I checked the usage of
spark.executor.extraJavaOptions, and it is as below (separated by blank space).
I will keep the code as is. If we want to support comma separated property, we
can just use String.split(",") to do the job. But the question is do we want
to support multiple format for the java options. Please let me know your
opinion.
# spark.executor.extraJavaOptions -XX:+PrintGCDetails -Dkey=value
-Dnumbers="one two three"
---
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]
