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 "Andrew Wang (JIRA)" <ji...@apache.org> on 2016/03/07 21:58:40 UTC
[jira] [Commented] (HADOOP-12901) Add warning log when
KMSClientProvider cannot create a connection to the KMS server
[ https://issues.apache.org/jira/browse/HADOOP-12901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183690#comment-15183690 ]
Andrew Wang commented on HADOOP-12901:
--------------------------------------
+1 LGTM pending Jenkins, thanks Xiao!
> Add warning log when KMSClientProvider cannot create a connection to the KMS server
> -----------------------------------------------------------------------------------
>
> Key: HADOOP-12901
> URL: https://issues.apache.org/jira/browse/HADOOP-12901
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Xiao Chen
> Assignee: Xiao Chen
> Priority: Minor
> Attachments: HADOOP-12901.01.patch
>
>
> Currently when failed to connect, one can only see logs at debug level with a vague {{SocketTimeoutException}}. (Luckily in the env I saw this, HADOOP-10015 was not present, so the last WARN log was printed.)
> {noformat}
> 2015-12-17 12:28:01,410 DEBUG org.apache.hadoop.security.UserGroupInformation: PrivilegedAction as:hdfs (auth:SIMPLE) from:org.apache.hadoop.crypto.key.kms.KMSClientProvider.createConnection(KMSClientProvider.java:477)
> 2015-12-17 12:28:01,469 WARN org.apache.hadoop.security.UserGroupInformation: PriviledgedActionException as:hdfs (auth:SIMPLE) cause:java.net.SocketTimeoutException: connect timed out
> {noformat}
> The issue was then fixed by opening up the KMS server port.
> This jira is to propose we add specific loggings in this case, to help user easily identify the problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)