[
https://issues.apache.org/jira/browse/HADOOP-12956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216395#comment-15216395
]
Chris Nauroth commented on HADOOP-12956:
----------------------------------------
bq. Has anyone spoken to the Log4J team about this?
>From what I can tell, the Log4J 2 domain model has changed so significantly
>that they don't consider it workable to attempt full backwards-compatibility
>with Log4J 1 style configuration. We could certainly ask again though.
I did have a brief conversation about losing our ability to switch logging
levels by passing -D arguments. They had a suggestion for plugging in to the
Log4J 2 internals to accomplish this, but I haven't had time to try it.
http://mail-archives.apache.org/mod_mbox/logging-log4j-user/201602.mbox/%3CD35E0663-D78B-4DAF-A26A-F5A27E8A14FC%40dslextreme.com%3E
I don't have any concrete information about the mixing problem at this point.
I expect it will require experimentation to figure out what is possible.
bq. Would the log tuning servlets work? They are invaluable for debugging live
services.
This is implemented with Commons Logging calls to change the levels. I didn't
investigate anything related to Commons Logging, because ZooKeeper has already
fully migrated to SLF4J as the logging API. Even if this doesn't work, I'd
expect it could be made to work by switching the code to call equivalent Log4J
2 APIs.
bq. we can still continue the move to SLF4J APIs, even for branch-2 code.
+1
> Inevitable Log4j2 migration via slf4j
> -------------------------------------
>
> Key: HADOOP-12956
> URL: https://issues.apache.org/jira/browse/HADOOP-12956
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Gopal V
>
> {{5 August 2015 --The Apache Logging Services™ Project Management Committee
> (PMC) has announced that the Log4j™ 1.x logging framework has reached its end
> of life (EOL) and is no longer officially supported.}}
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> A whole framework log4j2 upgrade has to be synchronized, partly for improved
> performance brought about by log4j2.
> https://logging.apache.org/log4j/2.x/manual/async.html#Performance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
