spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-6305) Add support for log4j 2.x to Spark
Date Wed, 29 Aug 2018 14:30:00 GMT

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

Steve Loughran commented on SPARK-6305:
---------------------------------------

bq. Could be possible that nobody is swapping it out for JUL since JUL is terrible.

I don't disagree, though if you get into the depths of kerberos debugging, you end up there.

regarding usable back-ends to SLF4J, there's logback, which is performant at the expense of
being async (pro: reduced impact of logging in locked areas; con: process crash can lose the
last logged bits)

Is the logging control in spark done only in tests, or in the production side of things? If
its only test-side, then log4j core can go on the CP there



> Add support for log4j 2.x to Spark
> ----------------------------------
>
>                 Key: SPARK-6305
>                 URL: https://issues.apache.org/jira/browse/SPARK-6305
>             Project: Spark
>          Issue Type: Improvement
>          Components: Build
>            Reporter: Tal Sliwowicz
>            Priority: Minor
>
> log4j 2 requires replacing the slf4j binding and adding the log4j jars in the classpath.
Since there are shaded jars, it must be done during the build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message