Re: Logging in executors

2016-04-18 Thread Carlos Rojas Matas
i, Apr 15, 2016 at 5:38 AM, Carlos Rojas Matas <cma...@despegar.com> > wrote: > >> Hi guys, >> >> any clue on this? Clearly the >> spark.executor.extraJavaOpts=-Dlog4j.configuration is not working on the >> executors. >> >> Thanks, >&

Re: Logging in executors

2016-04-15 Thread Carlos Rojas Matas
Hi guys, any clue on this? Clearly the spark.executor.extraJavaOpts=-Dlog4j.configuration is not working on the executors. Thanks, -carlos. On Wed, Apr 13, 2016 at 2:48 PM, Carlos Rojas Matas <cma...@despegar.com> wrote: > Hi Yong, > > thanks for your response. As I said in

Re: Logging in executors

2016-04-13 Thread Carlos Rojas Matas
Hi Yong, thanks for your response. As I said in my first email, I've tried both the reference to the classpath resource (env/dev/log4j-executor.properties) as the file:// protocol. Also, the driver logging is working fine and I'm using the same kind of reference. Below the content of my

Re: Logging in executors

2016-04-13 Thread Carlos Rojas Matas
Thanks for your response Ted. You're right, there was a typo. I changed it, now I'm executing: bin/spark-submit --master spark://localhost:7077 --conf "spark.driver.extraJavaOptions=-Dlog4j.configuration=env/dev/log4j-driver.properties" --conf

Logging in executors

2016-04-13 Thread Carlos Rojas Matas
Hi guys, I'm trying to enable logging in the executors but with no luck. According to the oficial documentation and several blogs, this should be done passing the "spark.executor.extraJavaOpts=-Dlog4j.configuration=[my-file]" to the spark-submit tool. I've tried both sending a reference to a