Re: disable log4j for spark-shell

2015-01-07 Thread Akhil
org.apache.log4j.Level Logger.getLogger(org).setLevel(Level.OFF) Logger.getLogger(akka).setLevel(Level.OFF) You won't see any logs after that. -- View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/disable-log4j-for-spark-shell-tp11278p21010.html Sent from the Apache

Re: disable log4j for spark-shell

2015-01-07 Thread Asim Jalis
org.apache.log4j.Level Logger.getLogger(org).setLevel(Level.OFF) Logger.getLogger(akka).setLevel(Level.OFF) You won't see any logs after that. -- View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/disable-log4j-for-spark-shell-tp11278p21010.html Sent from the Apache

Re: disable log4j for spark-shell

2014-11-11 Thread Ritesh Kumar Singh
= Logger.getRootLogger(); rootLogger.setLevel(Level.WARN); ... works for me -- View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/disable-log4j-for-spark-shell-tp11278p18535.html Sent from the Apache Spark User List mailing list archive at Nabble.com

Fwd: disable log4j for spark-shell

2014-11-11 Thread Ritesh Kumar Singh
-- Forwarded message -- From: Ritesh Kumar Singh riteshoneinamill...@gmail.com Date: Tue, Nov 11, 2014 at 2:18 PM Subject: Re: disable log4j for spark-shell To: lordjoe lordjoe2...@gmail.com Cc: u...@spark.incubator.apache.org go to your spark home and then into the conf

Re: disable log4j for spark-shell

2014-11-10 Thread hmxxyy
Tried --driver-java-options and SPARK_JAVA_OPTS, none of them worked Had to change the default one and rebuilt. -- View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/disable-log4j-for-spark-shell-tp11278p18513.html Sent from the Apache Spark User List mailing

Re: disable log4j for spark-shell

2014-11-10 Thread hmxxyy
Even after changing core/src/main/resources/org/apache/spark/log4j-defaults.properties to WARN followed by a rebuild, the log level is still INFO. Any other suggestions? -- View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/disable-log4j-for-spark-shell

Re: disable log4j for spark-shell

2014-11-10 Thread hmxxyy
$exprTyper=WARN log4j.logger.org.apache.spark.repl.SparkILoop$SparkILoopInterpreter=WARN Any suggestions? -- View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/disable-log4j-for-spark-shell-tp11278p18520.html Sent from the Apache Spark User List mailing list archive

Re: disable log4j for spark-shell

2014-11-10 Thread lordjoe
.nabble.com/disable-log4j-for-spark-shell-tp11278p18535.html Sent from the Apache Spark User List mailing list archive at Nabble.com. - To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user

Re: disable log4j for spark-shell

2014-08-27 Thread Yana
PRINT_SPARK_LAUNCH_COMMAND=1 very very useful when I'm trying to track a property) -- View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/disable-log4j-for-spark-shell-tp11278p12942.html Sent from the Apache Spark User List mailing list archive at Nabble.com

Re: disable log4j for spark-shell

2014-08-26 Thread Aaron
and modify the log level in there. The spark shells should pick this up. -- View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/disable-log4j-for-spark-shell-tp11278p12850.html Sent from the Apache Spark User List mailing list archive at Nabble.com

Re: disable log4j for spark-shell

2014-08-03 Thread Sean Owen
That's just a template. Nothing consults that file by default. It's looking inside the Spark .jar. If you edit core/src/main/resources/org/apache/spark/log4j-defaults.properties and rebuild Spark, it will pick up those changes. I think you could also use the JVM argument

Re: disable log4j for spark-shell

2014-08-03 Thread Patrick Wendell
If you want to customize the logging behavior - the simplest way is to copy conf/log4j.properties.tempate to conf/log4j.properties. Then you can go and modify the log level in there. The spark shells should pick this up. On Sun, Aug 3, 2014 at 6:16 AM, Sean Owen so...@cloudera.com wrote: