You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Michael Gummelt (JIRA)" <ji...@apache.org> on 2016/08/11 20:10:20 UTC

[jira] [Comment Edited] (SPARK-16784) Configurable log4j settings

    [ https://issues.apache.org/jira/browse/SPARK-16784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417857#comment-15417857 ] 

Michael Gummelt edited comment on SPARK-16784 at 8/11/16 8:10 PM:
------------------------------------------------------------------

{{log4j.debug=true}} only results in log4j printing its debugging messages.  It doesn't turn on debug logging for the application.


was (Author: mgummelt):
`log4j.debug=true` only results in log4j printing its debugging messages.  It doesn't turn on debug logging for the application.

> Configurable log4j settings
> ---------------------------
>
>                 Key: SPARK-16784
>                 URL: https://issues.apache.org/jira/browse/SPARK-16784
>             Project: Spark
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Michael Gummelt
>
> I often want to change the logging configuration on a single spark job.  This is easy in client mode.  I just modify log4j.properties.  It's difficult in cluster mode, because I need to modify the log4j.properties in the distribution in which the driver runs.  I'd like a way of setting this dynamically, such as a java system property.  Some brief searching showed that log4j doesn't seem to accept such a property, but I'd like to open up this idea for further comment.  Maybe we can find a solution.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org