[ 
https://issues.apache.org/jira/browse/HADOOP-18207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17928702#comment-17928702
 ] 

Piotr Karwasz commented on HADOOP-18207:
----------------------------------------

[~vjasani],

{quote}Certain things are not directly achieved by SLF4J like setting log level 
dynamically (we have dedicated servlet to make this happen). We also still have 
one custom appender that we will have to manage with log4j2 as well AFAIK, it's 
used by yarn: Log4jWarningErrorMetricsAppender.{quote}

Since many frameworks and standalone Java applications want to modify log 
levels, I started an [Apache Logging Admin 
API|https://github.com/apache/logging-admin] a couple of months ago. Its 
purpose is to replace all the code that depends on a particular logging backend 
in Kafka, Spring, Hadoop and others with backend independent code.

While the code seems almost ready to me, its release is still a couple of 
months (or quarters ;) ) away, since I need to analyze and conciliate the 
different needs that project have for log level modification: some projects 
like to list all **existing** loggers, some are only interested in those 
explicitly configured (existing or not). Some projects are interested in 
**effective** log levels, others are interested in the **configured** ones.

Feel free to review the (very simple) API to see if it fits your purpose and to 
post any remarks as [issues in the `logging-admin` 
repo|https://github.com/apache/logging-admin].

> 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
>            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]

Reply via email to