Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/299#discussion_r11793588
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -108,6 +110,21 @@ object SparkSubmit {
val sysProps = new HashMap[String, String]()
var childMainClass = ""
+ // Load system properties by default from the file, if present
+ if (appArgs.verbose) printStream.println(s"Using properties file:
${appArgs.propertiesFile}")
+ Option(appArgs.propertiesFile).foreach { filename =>
--- End diff --
I was trying to use spark.authenticate and it isn't being turned on.
This setting though I don't think will be able to be propagated since when
the executor starts it uses akka to talk back to the driver in order to get
those settings. It has to know ahead of time to use the secret. So perhaps
there are a few that need to be handled specially.
Looking at some other settings they are getting propagated properly.
I don't know if this is related to this jira but I'm also seeing weird
behavior when an application fails. The AM seems to be staying around even
though it finished with RM with failed. I'll try to look into this some more.
---
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.
---
