[
https://issues.apache.org/jira/browse/HADOOP-12956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419999#comment-15419999
]
Steve Loughran commented on HADOOP-12956:
-----------------------------------------
This is going to be fun. How about starting at discussion on common-dev &c?
some parts of the code (hdfs-client) are now log-backend neutral. Assuming all
uses of log4j APIs are in tests, maybe some wrapper could isolate the
conversion, or provide a flag to indicate if level tuning was allowed; test
cases could be skipped if not.
someone could then do an experimental branch using logback to see what happens.
It could also allow people to jump to log4j2 sooner rather than later, if they
so choose.
> 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: [email protected]
For additional commands, e-mail: [email protected]
