[
https://issues.apache.org/jira/browse/HADOOP-12956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213694#comment-15213694
]
Andrew Purtell commented on HADOOP-12956:
-----------------------------------------
We also evaluated a move to log4j2 for HBase on HBASE-10092, and likewise came
to the conclusion it is impossible to achieve backwards compatibility for
operators and tools. A change like this can't go in on a minor release. (At
least, HBase cannot do that, according to our published version compatibility
guidelines.) The killer issue is no backwards compatibility for the properties
based configuration files. Operators, not unreasonably, expect a minor or patch
version increment should continue to "just work" with existing configuration
files and tooling, not completely break all logging.
I see after LOG4J2-952 there is a "PropertiesConfigurationFactory", so _a_
properties based configuration file format is again possible, but this isn't
helpful and probably not desired because you get the limitations of a
properties file format without v1 compatibility.
> 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)
