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

Kitti Nanasi commented on HADOOP-16231:
---------------------------------------

Thanks for the comments [~smeng] and [~xyao], I will close this issue as Won't 
fix then.

> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to