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

Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2014/11/25 13:45:12 UTC

[jira] [Resolved] (SPARK-2007) Spark on YARN picks up hadoop log4j.properties even if SPARK_LOG4J_CONF is set

     [ https://issues.apache.org/jira/browse/SPARK-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen resolved SPARK-2007.
------------------------------
    Resolution: Fixed

Looks like this is resolved per the method Marcelo alludes to in the PR. That seems to be the correct current way to handle log4j.properties on YARN.

> Spark on YARN picks up hadoop log4j.properties even if SPARK_LOG4J_CONF is set
> ------------------------------------------------------------------------------
>
>                 Key: SPARK-2007
>                 URL: https://issues.apache.org/jira/browse/SPARK-2007
>             Project: Spark
>          Issue Type: Bug
>          Components: YARN
>    Affects Versions: 1.0.0
>            Reporter: Issac Buenrostro
>
> When running Spark on YARN, with SPARK_LOG4J_CONF environment variable set, containers might still pick up a different log4j configuration.
> spark-yarn will create a local resource in YARN called log4j.properties, which is included in the classpath. However, there might be other log4j.properties files in the classpath which might be chosen instead.



--
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