hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-15581) Set default jetty log level to INFO in KMS
Date Mon, 09 Jul 2018 19:50:00 GMT

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

Hudson commented on HADOOP-15581:
---------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14544 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/14544/])
HADOOP-15581. Set default jetty log level to INFO in KMS. Contributed by (xiao: rev 895845e9b0d7ac49da36b5cf773c6330afe4f3e0)
* (edit) hadoop-common-project/hadoop-kms/src/main/conf/kms-log4j.properties
* (edit) hadoop-common-project/hadoop-kms/src/test/resources/log4j.properties


> Set default jetty log level to INFO in KMS
> ------------------------------------------
>
>                 Key: HADOOP-15581
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15581
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 3.1.0
>            Reporter: Kitti Nanasi
>            Assignee: Kitti Nanasi
>            Priority: Major
>              Labels: kms
>             Fix For: 3.2.0
>
>         Attachments: HADOOP-15581.001.patch
>
>
> During debugging KMS, jetty is printing lots of things at DEBUG/TRACE level. These isn't
helpful usually unless someone is debugging the web server part, so we should consider putting
an explicit INFO log for them, similar to https://issues.apache.org/jira/browse/HADOOP-14515.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message