[
https://issues.apache.org/jira/browse/HADOOP-18631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696043#comment-17696043
]
ASF GitHub Bot commented on HADOOP-18631:
-----------------------------------------
ayushtkn commented on PR #5418:
URL: https://github.com/apache/hadoop/pull/5418#issuecomment-1453066662
There is a test failing ``TestFsck`` most probably due to this change.
https://ci-hadoop.apache.org/view/Hadoop/job/hadoop-qbt-trunk-java8-linux-x86_64/1153/testReport/junit/org.apache.hadoop.hdfs.server.namenode/TestFsck/org_apache_hadoop_hdfs_server_namenode_TestFsck/
Didn't check this and related changes. But looks like same path is used for
``AUDIT_LOG_FILE`` by two tests and may be one wiped out before other could
attempt to do so...
Please raise an addendum and fix the test if it is indeed related to this.
Will leave it further to @jojochuang....
> 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]
