[
https://issues.apache.org/jira/browse/HADOOP-15698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597067#comment-16597067
]
Xiao Chen edited comment on HADOOP-15698 at 8/30/18 5:11 AM:
-------------------------------------------------------------
Committed to trunk as well as branch-3.[0-1] (since I believe this is a
regression from HADOOP-13597).
Thanks Kitti for the nice fix, and Ajay / Daniel for the review comments!
was (Author: xiaochen):
Committed to trunk as well as branch-3.[0-1] (since I believe this is a
regression from HADOOP-13597).
Thanks Kitti for the nice fix, and Ajay / Daniel for the comments!
> KMS log4j is not initialized properly at startup
> ------------------------------------------------
>
> Key: HADOOP-15698
> URL: https://issues.apache.org/jira/browse/HADOOP-15698
> Project: Hadoop Common
> Issue Type: Bug
> Components: kms
> Affects Versions: 3.1.0
> Reporter: Kitti Nanasi
> Assignee: Kitti Nanasi
> Priority: Major
> Fix For: 3.2.0, 3.0.4, 3.1.2
>
> Attachments: HADOOP-15698.001.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
