Hi Tobias, With the current Yarn code, packaging the configuration in your app's jar and adding the "-Dlog4j.configuration=log4jConf.xml" argument to the extraJavaOptions configs should work.
That's not the recommended way for get it to work, though, since this behavior may change in the future. The recommended way is to do what Sean mentions - upload the configuration as a separate file. If you upload a "log4j.properties" file that's all you need, but if you really want to use an XML config file you'll also need to pass the extra options to the driver and executors. On Thu, Nov 20, 2014 at 12:20 AM, Tobias Pfeiffer <t...@preferred.jp> wrote: > Hi, > > I am using spark-submit to submit my application jar to a YARN cluster. I > want to deliver a single jar file to my users, so I would like to avoid to > tell them "also, please put that log4j.xml file somewhere and add that path > to the spark-submit command". > > I thought it would be sufficient that my application jar file contains a > log4j.xml file, but that does not seem to be the case. If I don't add a > log4j.xml file to the classpath before launching spark-submit, the one > bundled with spark will be used -- which has a negative influence on my > program execution. Is there any way I can tell spark-submit to use the > log4j configuration bundled in my jar file? > > Thanks > Tobias -- Marcelo --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user-h...@spark.apache.org
