You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Don Kim (JIRA)" <ji...@apache.org> on 2008/08/11 21:50:46 UTC
[jira] Created: (HADOOP-3934) Update log4j from 1.2.13 to 1.2.15
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.
[jira] Updated: (HADOOP-3934) Update log4j from 1.2.13 to 1.2.15
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley updated HADOOP-3934:
----------------------------------
Fix Version/s: (was: 0.19.0)
0.18.1
This was needed for 0.18 deployment. I also included the fix from HADOOP-4037.
> 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
> Assignee: Owen O'Malley
> 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.
[jira] Commented: (HADOOP-3934) Update log4j from 1.2.13 to 1.2.15
Posted by "Robert Chansler (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (HADOOP-3934) Update log4j from 1.2.13 to 1.2.15
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630181#action_12630181 ]
Hudson commented on HADOOP-3934:
--------------------------------
Integrated in Hadoop-trunk #600 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/600/])
> 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
> Assignee: Owen O'Malley
> 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.
[jira] Updated: (HADOOP-3934) Update log4j from 1.2.13 to 1.2.15
Posted by "Allen Wittenauer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer updated HADOOP-3934:
-------------------------------------
Affects Version/s: 0.18.0
> 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
>
> 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.
[jira] Commented: (HADOOP-3934) Update log4j from 1.2.13 to 1.2.15
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624805#action_12624805 ]
Hudson commented on HADOOP-3934:
--------------------------------
Integrated in Hadoop-trunk #581 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/581/])
> 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
> Assignee: Owen O'Malley
> Priority: Blocker
> Fix For: 0.19.0
>
>
> 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.
[jira] Commented: (HADOOP-3934) Update log4j from 1.2.13 to 1.2.15
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623348#action_12623348 ]
Steve Loughran commented on HADOOP-3934:
----------------------------------------
> Hadoop is built with a non-standard version of Log4J
I don't see that
hadoop-core> md5sum lib/log4j-1.2.13.jar
52169b4a318e3246483f39f62b84b948 lib/log4j-1.2.13.jar
~/.ivy2/cache/log4j/log4j/jars> md5sum log4j-1.2.13.jar
52169b4a318e3246483f39f62b84b948 log4j-1.2.13.jar
Looks like a standard release to me, or at least to md5sum.
> 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.
[jira] Updated: (HADOOP-3934) Update log4j from 1.2.13 to 1.2.15
Posted by "Allen Wittenauer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer updated HADOOP-3934:
-------------------------------------
Priority: Blocker (was: Major)
> 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
> Priority: Blocker
>
> 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.
[jira] Updated: (HADOOP-3934) Update log4j from 1.2.13 to 1.2.15
Posted by "Nigel Daley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nigel Daley updated HADOOP-3934:
--------------------------------
Fix Version/s: 0.18.1
> 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.
[jira] Commented: (HADOOP-3934) Update log4j from 1.2.13 to 1.2.15
Posted by "Allen Wittenauer (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (HADOOP-3934) Update log4j from 1.2.13 to 1.2.15
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley resolved HADOOP-3934.
-----------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.18.1)
0.19.0
Assignee: Owen O'Malley
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.
> 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
> Assignee: Owen O'Malley
> Priority: Blocker
> Fix For: 0.19.0
>
>
> 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.