[
https://issues.apache.org/jira/browse/HADOOP-18207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724751#comment-17724751
]
ASF GitHub Bot commented on HADOOP-18207:
-----------------------------------------
virajjasani commented on code in PR #5503:
URL: https://github.com/apache/hadoop/pull/5503#discussion_r1199923215
##########
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/log/LogLevel.java:
##########
@@ -349,7 +348,7 @@ public void doGet(HttpServletRequest request,
HttpServletResponse response
}
if (GenericsUtil.isLog4jLogger(logName)) {
Review Comment:
Thanks @Apache9 for raising this point btw.
let me paste my
[comment](https://issues.apache.org/jira/browse/HADOOP-16206?focusedCommentId=17702846&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17702846)
from parent jira, the jira has too many comments so can be easily ignored :)
_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._
> Introduce hadoop-logging module
> -------------------------------
>
> Key: HADOOP-18207
> URL: https://issues.apache.org/jira/browse/HADOOP-18207
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Assignee: Viraj Jasani
> Priority: Major
> Labels: pull-request-available
>
> There are several goals here:
> # Provide the ability to change log level, get log level, etc.
> # Place all the appender implementation(?)
> # Hide the real logging implementation.
> # Later we could remove all the log4j references in other hadoop module.
> # Move as much log4j usage to the module as possible.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
