hadoop-common-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] (HADOOP-12956) Inevitable Log4j2 migration via slf4j
Date Tue, 03 Jan 2017 10:29:58 GMT

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

Steve Loughran commented on HADOOP-12956:
-----------------------------------------

Certainly moving to the slf4j APIs is something to do. The simple approach: just change the
type of the log used. The better one: at least for info and above levels, just rely on slf4
varargs expansion. 

if you look at how log4j is explicitly used in the code, its in some of the tests, where its
log is cranked back. Something will need to be done for log4j 2 there

> Inevitable Log4j2 migration via slf4j
> -------------------------------------
>
>                 Key: HADOOP-12956
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12956
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Gopal V
>
> {{5 August 2015 --The Apache Logging Services™ Project Management Committee (PMC) has
announced that the Log4j™ 1.x logging framework has reached its end of life (EOL) and is
no longer officially supported.}}
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> A whole framework log4j2 upgrade has to be synchronized, partly for improved performance
brought about by log4j2.
> https://logging.apache.org/log4j/2.x/manual/async.html#Performance



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message