RE: Logging in executors

code. That also worked for us, but we went the extraJavaOptions route as it was less invasive on the application side. -Ashic. Date: Mon, 18 Apr 2016 10:32:03 -0300 Subject: Re: Logging in executors From: cma...@despegar.com To: yuzhih...@gmail.com CC: user@spark.apache.org Thanks Ted, already check

Re: Logging in executors

og4j/1.2/manual.html >>>>> >>>>> When you specify the log4j.configuration=my_custom.properties, you >>>>> have 2 option: >>>>> >>>>> 1) the my_custom.properties has to be in the jar (or in the >>>>> classpat

Re: Logging in executors

s, you have >>>> 2 option: >>>> >>>> 1) the my_custom.properties has to be in the jar (or in the classpath). >>>> In your case, since you specify the package path, you need to make sure >>>> they are matched in your jar file >>>> 2) use like log4j.configur

Re: Logging in executors

r case, since you specify the package path, you need to make sure >>> they are matched in your jar file >>> 2) use like log4j.configuration=file:///tmp/my_custom.properties. In >>> this way, you need to make sure file my_custom.properties exists in /tmp >>> folder on ALL

Re: Logging in executors

ke sure >> they are matched in your jar file >> 2) use like log4j.configuration=file:///tmp/my_custom.properties. In this >> way, you need to make sure file my_custom.properties exists in /tmp folder >> on ALL of your worker nodes. >> >> Yong >> >> -

Re: Logging in executors

my_custom.properties. In this > way, you need to make sure file my_custom.properties exists in /tmp folder > on ALL of your worker nodes. > > Yong > > ---------- > Date: Wed, 13 Apr 2016 14:18:24 -0300 > Subject: Re: Logging in executors > From: c

RE: Logging in executors

sure file my_custom.properties exists in /tmp folder on ALL of your worker nodes. Yong Date: Wed, 13 Apr 2016 14:18:24 -0300 Subject: Re: Logging in executors From: cma...@despegar.com To: yuzhih...@gmail.com CC: user@spark.apache.org Thanks for your response Ted. You're right, there was a typo

Re: Logging in executors

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

Re: Logging in executors

bq. --conf "spark.executor.extraJavaOptions=-Dlog4j. configuration=env/dev/log4j-driver.properties" I think the above may have a typo : you refer to log4j-driver.properties in both arguments. FYI On Wed, Apr 13, 2016 at 8:09 AM, Carlos Rojas Matas wrote: > Hi guys, > >