[
https://issues.apache.org/jira/browse/OOZIE-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16643738#comment-16643738
]
Robert Kanter commented on OOZIE-3136:
--------------------------------------
+1 on not going to log4j2 until Oozie 6. Cleaning up our logging story and
using the bridge in the meantime is probably a good idea.
Our logging is somewhat brittle because of the log streaming. IIRC, we require
log files to be rolled every hour because the log streaming makes some
assumptions about that to improve performance. Similarly, logs can be
automatically gzipped, but we also make assumptions about that and the
filenames. That's part of what the {{OozieRollingPolicy}} was for (it used to
be messier before I added it :)). So if we need to get rid of
{{OozieRollingPolicy}}, then we'll need to either replace it with something
equivalent, or refactor the log streaming code to be more flexible.
> 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)
