Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 0.18.0
    • Fix Version/s: 0.18.1
    • Component/s: None
    • Labels:
      None

      Description

      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).

        Activity

        Hide
        Hudson added a comment -
        Show
        Hudson added a comment - Integrated in Hadoop-trunk #600 (See http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/600/ )
        Hide
        Owen O'Malley added a comment -

        This was needed for 0.18 deployment. I also included the fix from HADOOP-4037.

        Show
        Owen O'Malley added a comment - This was needed for 0.18 deployment. I also included the fix from HADOOP-4037 .
        Hide
        Hudson added a comment -
        Show
        Hudson added a comment - Integrated in Hadoop-trunk #581 (See http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/581/ )
        Hide
        Owen O'Malley added a comment -

        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.

        Show
        Owen O'Malley added a comment - 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.
        Hide
        steve_l added a comment -

        > 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.

        Show
        steve_l added a comment - > 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.
        Hide
        Robert Chansler added a comment -

        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.)

        Show
        Robert Chansler added a comment - 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.)
        Hide
        Allen Wittenauer added a comment -

        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.]

        Show
        Allen Wittenauer added a comment - 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.]

          People

          • Assignee:
            Owen O'Malley
            Reporter:
            Don Kim
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development