[
https://issues.apache.org/jira/browse/OOZIE-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16643018#comment-16643018
]
Peter Cseh commented on OOZIE-3136:
-----------------------------------
I don't really see a compelling reason for upgrading to Log4j2 in the short
term. It has better performance characteristics, but I don't recall any issues
with Oozie's logging performance. I think moving to SLF4J is a good approach
though as it will make the future Log4J2 migration easier.
Really, with proper Slf4j usage, the log4j version shouldn't really matter.
We're using a very old logger though to support log streaming across
active-active Oozie servers in case of HA. That will be probably the hardest
part of the migration and I think we could address that in slf4j as well.
> Upgrade from Log4j 1.x to 2.x
> -----------------------------
>
> Key: OOZIE-3136
> URL: https://issues.apache.org/jira/browse/OOZIE-3136
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Attila Sasvari
> Assignee: Julia Kinga Marton
> Priority: Major
>
> {{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
> We should upgrade from Log4j 1.x to 2.x . Perhaps we could use slf4j .
> Related tickets: MAPREDUCE-6983, HADOOP-12956, OOZIE-3135
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
