You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Patrick Wendell (JIRA)" <ji...@apache.org> on 2014/08/15 22:49:18 UTC
[jira] [Comment Edited] (SPARK-2858) Default log4j configuration no
longer seems to work
[ https://issues.apache.org/jira/browse/SPARK-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098148#comment-14098148 ]
Patrick Wendell edited comment on SPARK-2858 at 8/15/14 8:48 PM:
-----------------------------------------------------------------
What I mean is that when I don't include any log4j.properties file, Spark fails to use its own default configuration.
was (Author: pwendell):
What I mean is that when I don't include any log4j.properties file, Spark fails to use it's own default configuration.
> Default log4j configuration no longer seems to work
> ---------------------------------------------------
>
> Key: SPARK-2858
> URL: https://issues.apache.org/jira/browse/SPARK-2858
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Reporter: Patrick Wendell
>
> For reasons unknown this doesn't seem to be working anymore. I deleted my log4j.properties file and did a fresh build and it noticed it still gave me a verbose stack trace when port 4040 was contented (which is a log we silence in the conf). I actually think this was an issue even before [~sowen]'s changes, so not sure what's up.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org