[
https://issues.apache.org/jira/browse/HADOOP-18631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696551#comment-17696551
]
ASF GitHub Bot commented on HADOOP-18631:
-----------------------------------------
ayushtkn commented on PR #5451:
URL: https://github.com/apache/hadoop/pull/5451#issuecomment-1455040719
Interfere means: it would only capture audit log pushed by that class and
won’t capture anything from other classes being run in parallel, doing the same
appender thing or the file thing?
A simple test could be to write a long running test which creates this
appender and just writes whatever is there in the output, when other test runs
in parallel, both with File logic and appender logic.
if that tests doesn’t get any output. We are sorted.
> 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: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
