[
https://issues.apache.org/jira/browse/OOZIE-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16643051#comment-16643051
]
Peter Bacsko commented on OOZIE-3136:
-------------------------------------
I do agree that we don't have to upgrade right now. That would be a much bigger
undertaking, taking at least weeks to finish and then test properly. Backward
compatibility must be preserved.
bq. if the user has a fat JAR consisting also of log4j12 classes that are
versions incompatible w/ the Oozie server
Fat jar has always been a problem and right now there's not much we can do
about it (we could mitigate it to a certain degree with better classloader
isolation, but again, that's not straightforward). We've seen conflicting
Guavas as well. Also, the YARN side is a different story, we don't even use
loggers there, just sysout. On a separate note, we shall focus on those sysouts
too, it doesn't look good :)
bq. I don't recall any issues with Oozie's logging performance
I do remember one instance and I'm sure that so do you: when we enabled full
DEBUG loggin in the tests, that completely choked log4j and upstream tests
timed out. Pretty nasty. Indeed, lot of output was generated, but still, such
things should not happen with a well-performing logging library.
Just the fact that we depend on an ancient library that hasn't been actively
maintained in the last 3-4 years is alone a good reason for an upgrade -
probably in Oozie 6.0.
> 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)
