You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Kitti Nanasi (JIRA)" <ji...@apache.org> on 2019/04/26 08:41:00 UTC
[jira] [Updated] (HADOOP-16231) Reduce KMS error logging severity
from WARN to INFO
[ https://issues.apache.org/jira/browse/HADOOP-16231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kitti Nanasi updated HADOOP-16231:
----------------------------------
Resolution: Won't Fix
Status: Resolved (was: Patch Available)
> Reduce KMS error logging severity from WARN to INFO
> ---------------------------------------------------
>
> Key: HADOOP-16231
> URL: https://issues.apache.org/jira/browse/HADOOP-16231
> Project: Hadoop Common
> Issue Type: Improvement
> Components: kms
> Affects Versions: 3.2.0
> Reporter: Kitti Nanasi
> Assignee: Kitti Nanasi
> Priority: Trivial
> Attachments: HDFS-14404.001.patch
>
>
> When the KMS is deployed as an HA service and a failure occurs the current error severity in the client code appears to be WARN. It can result in excessive errors despite the fact that another instance may succeed.
> Maybe this log level can be adjusted in only the load balancing provider.
> {code}
> 19/02/27 05:10:10 WARN kms.LoadBalancingKMSClientProvider: KMS provider at [https://example.com:16000/kms/v1/] threw an IOException [java.net.ConnectException: Connection refused (Connection refused)]!!
> 19/02/12 20:50:09 WARN kms.LoadBalancingKMSClientProvider: KMS provider at [https://example.com:16000/kms/v1/] threw an IOException:
> java.io.IOException: java.lang.reflect.UndeclaredThrowableException
> {code}
--
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