You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2023/03/02 00:03:00 UTC

[jira] [Resolved] (HADOOP-18648) Avoid loading kms log4j properties dynamically by KMSWebServer

     [ https://issues.apache.org/jira/browse/HADOOP-18648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wei-Chiu Chuang resolved HADOOP-18648.
--------------------------------------
    Fix Version/s: 3.4.0
       Resolution: Fixed

> Avoid loading kms log4j properties dynamically by KMSWebServer
> --------------------------------------------------------------
>
>                 Key: HADOOP-18648
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18648
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0
>
>
> Log4j2 does not support loading of log4j properties (/xml/json/yaml) dynamically by applications. It no longer supports overriding the loading of properties using "log4j.defaultInitOverride" the way log4j1 does.
> For KMS, instead of loading the properties file dynamically, we should add the log4j properties file as part of HADOOP_OPTS.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org