You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Joshua Caplan (Jira)" <ji...@apache.org> on 2021/02/06 03:14:01 UTC
[jira] [Commented] (HADOOP-12956) Inevitable Log4j2 migration via
slf4j
[ https://issues.apache.org/jira/browse/HADOOP-12956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280061#comment-17280061 ]
Joshua Caplan commented on HADOOP-12956:
----------------------------------------
is this ever going to happen? is there a branch of Hadoop that eschews backward compatibility but uses Log4J2?
This is no longer about end of life or performance. The product cannot be used by organizations that have strict requirements about open source with known vulnerabilities.
See [CVE-2019-17571|https://nvd.nist.gov/vuln/detail/CVE-2019-17571].
> 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 Vijayaraghavan
> Assignee: Haohui Mai
> Priority: Major
>
> {{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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org