|
I surveyed some of the usual suspects, and failed to confirm that this is an urgent performance issue. Satisfactory performance was reported in one large test.
That said, moving to the next version of Log4J is a Good Thing for the reasons reported by Don. (The reason that this is a non-trivial upgrade is that Hadoop is built with a non-standard version of Log4J. Transition to a released version requires some deliberation.) > Hadoop is built with a non-standard version of Log4J
I don't see that hadoop-core> md5sum lib/log4j-1.2.13.jar ~/.ivy2/cache/log4j/log4j/jars> md5sum log4j-1.2.13.jar Looks like a standard release to me, or at least to md5sum. I just committed this to trunk after running unit tests. If we feel we need to add this to 18.1, that can be done after 18.0 is tagged.
Integrated in Hadoop-trunk #581 (See http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/581/
 ) This was needed for 0.18 deployment. I also included the fix from
Integrated in Hadoop-trunk #600 (See http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/600/
) |
|||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Closed
Blocker
Update log4j from 1.2.13 to 1.2.15
Given the reported performance hits that we're seeing with log4j and audit logging, I don't think it is going to be possible for us to upgrade to 0.18 and turn on audit logging without this fix in place. [... and we desperately need audit logging for metrics and security reasons.]