[
https://issues.apache.org/jira/browse/HADOOP-12901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183813#comment-15183813
]
Hudson commented on HADOOP-12901:
---------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9439 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9439/])
HADOOP-12901. Add warning log when KMSClientProvider cannot create a (wang: rev
391da36d93358038c50c15d91543f6c765fa0471)
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/crypto/key/kms/KMSClientProvider.java
> 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
> Fix For: 2.8.0
>
> 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)
