[
https://issues.apache.org/jira/browse/HADOOP-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623065#action_12623065
]
Robert Chansler commented on HADOOP-3934:
-----------------------------------------
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.)
> Update log4j from 1.2.13 to 1.2.15
> ----------------------------------
>
> Key: HADOOP-3934
> URL: https://issues.apache.org/jira/browse/HADOOP-3934
> Project: Hadoop Core
> Issue Type: Improvement
> Affects Versions: 0.18.0
> Reporter: Don Kim
> Priority: Blocker
> Fix For: 0.18.1
>
>
> Hadoop is currently using log4j version 1.2.13 and this version does not
> support the use of a non-default syslog port when specifying the syslog
> server destination. Syslogging is important to us and even more so with
> audit logging introduced in hadoop-0.18. The current released version of
> log4j is 1.2.15 which does support the use of specifying a non-default syslog
> port (introduced in log4j 1.2.14) as well as many other syslog enhancements
> and fixes (http://logging.apache.org/log4j/1.2/changes-report.html).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
