[jira] [Commented] (SPARK-3782) Direct use of log4j in AkkaUtils interferes with certain logging configurations

["Sean Owen (JIRA)" <ji...@apache.org>]

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

Sean Owen commented on SPARK-3782:
----------------------------------

Aha, I think there's a good point here. 

Looks like this method was added to the log4j shim in slf4j 1.7.6: https://github.com/qos-ch/slf4j/commit/004b5d4879a079f3d6f610b7fe339a0fad7d4831 

So it should be fine if you use log4j-over-slf4j 1.7.6+ in your app. Spark references slf4j 1.7.5 though. Although I don't think it will matter if you use a different version, we could update Spark's slf4j to 1.7.6 at least, to be really consistent. 1.7.10 is the latest in fact.

> Direct use of log4j in AkkaUtils interferes with certain logging configurations 
> --------------------------------------------------------------------------------
>
>                 Key: SPARK-3782
>                 URL: https://issues.apache.org/jira/browse/SPARK-3782
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>            Reporter: Martin Gilday
>
> AkkaUtils is calling setLevel on Logger from log4j. This causes issues when using another implementation of SLF4J such as logback as log4j-over-slf4j.jars implementation of this class does not contain this method on Logger.



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