[
https://issues.apache.org/jira/browse/HADOOP-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621632#action_12621632
]
Allen Wittenauer commented on HADOOP-3934:
------------------------------------------
I'm going to mark this as a blocker for 0.18.
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.]
> 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
> Reporter: Don Kim
>
> 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.
