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

KMS log4j is not initialized properly at startup

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 3.1.0
    • 3.2.0, 3.0.4, 3.1.2
    • kms
    • None
    • 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

        1. HADOOP-15698.001.patch
          7 kB
          Kitti Nanasi

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            knanasi Kitti Nanasi
            knanasi Kitti Nanasi
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment