hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajay Kumar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-15698) KMS startup logs don't show
Date Wed, 29 Aug 2018 00:14:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-15698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595774#comment-16595774

Ajay Kumar commented on HADOOP-15698:

[~xiaochen] agree, +1
[~templedf] " We don't generally worry about testing logging" yes but this patch itself is
about logging, hence the question.

> KMS startup logs don't show
> ---------------------------
>                 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
>         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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message