[
https://issues.apache.org/jira/browse/HADOOP-12956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946583#comment-15946583
]
Haohui Mai commented on HADOOP-12956:
-------------------------------------
In our production environment we saw various bottlenecks in NN due to log4j,
even with asynchronous logging turned on.
Having the option of moving towards log4j2 via slf4j, even it means that it is
backward-incompatible is still hugely beneficial.
I think it is still possible to pull it off although it will touch a lot of
code:
{noformat}
$ find . -name "*.java"|xargs grep "log4j\."|grep "import" -c
289
$ find . -name "*.java"|xargs grep "log4j\."|grep "import"|grep "/test/" -c
242
{noformat}
> 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
