You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Andrew Ash (JIRA)" <ji...@apache.org> on 2014/09/07 10:23:29 UTC
[jira] [Commented] (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=14124838#comment-14124838 ]
Andrew Ash commented on SPARK-2858:
-----------------------------------
Josh mentions in that ticket that the Spark EC2 AMI might put the HDFS log4j ahead of Spark's and steal the priority. Were you running via the EC2 scripts?
https://issues.apache.org/jira/browse/SPARK-2913?focusedCommentId=14104366&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14104366
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org