[HADOOP-15698] KMS log4j is not initialized properly at startup

• 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
• Target Version/s: 3.2.0
• Hadoop Flags: Reviewed
• Assignee: Kitti Nanasi
• Reporter: Kitti Nanasi
• Created: 27/Aug/18 09:59
• Updated: 31/Aug/18 02:43
• Resolved: 30/Aug/18 05:10

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.

Issue Links

• is blocked by: HADOOP-13597 Switch KMS from Tomcat to Jetty