[ https://issues.apache.org/jira/browse/HADOOP-16206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17702846#comment-17702846 ]
Viraj Jasani commented on HADOOP-16206: --------------------------------------- FYI, we use some of the core log4j APIs specifically meant to be used for properties based config and log4j2 has this support removed as they were meant to be private usage. Moreover, we also programmatically set monitor interval for dynamic log4j file changes in httpfs server. This is also no longer supported as that is also meant to be kept in config only (properties, xml, json, yaml etc). I have started this thread with log4j dev/user group for the same [https://lists.apache.org/thread/4l7oyk84jpj6br0sn4ymofdcbgfxmtqp] So far, the only recommended solution provided by them is to configure monitor interval in log4j properties only (i.e. user provided custom log4j properties, in case of httpfs Server), and use Configurator API for the properties file specific usage we have. > Migrate from Log4j1 to Log4j2 > ----------------------------- > > Key: HADOOP-16206 > URL: https://issues.apache.org/jira/browse/HADOOP-16206 > Project: Hadoop Common > Issue Type: Task > Affects Versions: 3.3.0 > Reporter: Akira Ajisaka > Assignee: Viraj Jasani > Priority: Major > Attachments: HADOOP-16206-wip.001.patch > > > This sub-task is to remove log4j1 dependency and add log4j2 dependency. -- 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