[jira] [Commented] (HADOOP-12956) Inevitable Log4j2 migration via slf4j

["Chris Nauroth (JIRA)" <ji...@apache.org>]

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

Chris Nauroth commented on HADOOP-12956:
----------------------------------------

I recently explored a Log4J 2 migration for ZooKeeper.  My notes and a work-in-progress patch are on ZOOKEEPER-2342.  We came to the conclusion that it's impossible to achieve backwards-compatibility for operators and tools that edit Log4J configuration, so I've put the work on hold at this point.

I agree with the use of "inevitable" in the JIRA title, but it's going to be a very difficult change, likely requiring ecosystem coordination.

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