[
https://issues.apache.org/jira/browse/HADOOP-18631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700896#comment-17700896
]
ASF GitHub Bot commented on HADOOP-18631:
-----------------------------------------
jojochuang commented on PR #5451:
URL: https://github.com/apache/hadoop/pull/5451#issuecomment-1470965254
+1 merging this one. In any case, it is unfortunately impossible to upgrade
to log4j2 without any friction. We do what we can do at code review, but
ultimately it's up to the downstream application developers to adopt and
change. Most likely we'll find issues during integration tests but I don't see
any other way.
> Migrate Async appenders to log4j properties
> -------------------------------------------
>
> Key: HADOOP-18631
> URL: https://issues.apache.org/jira/browse/HADOOP-18631
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
>
> Before we can upgrade to log4j2, we need to migrate async appenders that we
> add "dynamically in the code" to the log4j.properties file. Instead of using
> core/hdfs site configs, log4j properties or system properties should be used
> to determine if the given logger should use async appender.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
