Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-15698

KMS log4j is not initialized properly at startup

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.0
    • Fix Version/s: 3.2.0, 3.0.4, 3.1.2
    • Component/s: kms
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      During KMs startup, log4j logs don't show up resulting in important logs getting omitted. This happens because log4 initialisation only happens in KMSWebApp#contextInitialized and logs written before that don't show up.

      For example the following log never shows up:

      https://github.com/apache/hadoop/blob/a55d6bba71c81c1c4e9d8cd11f55c78f10a548b0/hadoop-common-project/hadoop-auth/src/main/java/org/apache/hadoop/security/authentication/util/ZKSignerSecretProvider.java#L197-L199

      Another example is that the KMS startup message never shows up in the kms logs.

      Note that this works in the unit tests, because MiniKMS sets the log4j system property.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                knanasi Kitti Nanasi
                Reporter:
                knanasi Kitti Nanasi
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: