Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1844#issuecomment-51624727
@shivaram Good points. We probably want Spark's log4j.properties to be
used for interactive shells and when launching Spark standalone masters and
workers, but I can see cases where the user might prefer if spark-submit used
the log4j.properties file from their application JAR.
Even if we decide to only change the code in spark-ec2, I think we should
still update the documentation to be clearer about possible sources of
log4j.properties (and maybe explain how to debug these issues with
`SPARK_PRINT_LAUNCH_COMMAND=1`).
I can look into this, but do you know whether the application JAR takes
precedence over the other classpath entries so that its log4j.properties file
will always be preferred?
---
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]
