[
https://issues.apache.org/jira/browse/HADOOP-13750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606883#comment-15606883
]
Xiao Chen commented on HADOOP-13750:
------------------------------------
Thanks John for filing the issue. I think the HTTP 400 means the KMS server
(minikms in this case) hasn't started yet.
> TestKMS#testKMSProvider is flaky
> --------------------------------
>
> Key: HADOOP-13750
> URL: https://issues.apache.org/jira/browse/HADOOP-13750
> Project: Hadoop Common
> Issue Type: Bug
> Components: kms
> Affects Versions: 3.0.0-alpha2
> Environment: Ubuntu 14.04
> OpenJDK 1.8.0_91
> Reporter: John Zhuge
> Priority: Minor
>
> Saw it 1 out of 110 tests, so extremely rare. File it anyway for the record.
> Also note that the test slave was just resumed.
> {noformat}
> 22:03:49 Running org.apache.hadoop.crypto.key.kms.server.TestKMS
> 2016-10-23 22:05:34 Tests run: 26, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed: 105.34 sec <<< FAILURE! - in
> org.apache.hadoop.crypto.key.kms.server.TestKMS
> 2016-10-23 22:05:34
> testKMSProvider(org.apache.hadoop.crypto.key.kms.server.TestKMS) Time
> elapsed: 1.439 sec <<< ERROR!
> 2016-10-23 22:05:34 java.io.IOException: HTTP status [400], message [Bad
> Content-Type header value: '']
> 2016-10-23 22:05:34 at
> org.apache.hadoop.util.HttpExceptionUtils.validateResponse(HttpExceptionUtils.java:169)
> 2016-10-23 22:05:34 at
> org.apache.hadoop.crypto.key.kms.KMSClientProvider.call(KMSClientProvider.java:596)
> 2016-10-23 22:05:34 at
> org.apache.hadoop.crypto.key.kms.KMSClientProvider.call(KMSClientProvider.java:585)
> 2016-10-23 22:05:34 at
> org.apache.hadoop.crypto.key.kms.KMSClientProvider.call(KMSClientProvider.java:554)
> 2016-10-23 22:05:34 at
> org.apache.hadoop.crypto.key.kms.KMSClientProvider.getKeyVersion(KMSClientProvider.java:625)
> 2016-10-23 22:05:34 at
> org.apache.hadoop.crypto.key.kms.LoadBalancingKMSClientProvider$6.call(LoadBalancingKMSClientProvider.java:226)
> 2016-10-23 22:05:34 at
> org.apache.hadoop.crypto.key.kms.LoadBalancingKMSClientProvider$6.call(LoadBalancingKMSClientProvider.java:223)
> 2016-10-23 22:05:34 at
> org.apache.hadoop.crypto.key.kms.LoadBalancingKMSClientProvider.doOp(LoadBalancingKMSClientProvider.java:95)
> 2016-10-23 22:05:34 at
> org.apache.hadoop.crypto.key.kms.LoadBalancingKMSClientProvider.getKeyVersion(LoadBalancingKMSClientProvider.java:223)
> 2016-10-23 22:05:34 at
> org.apache.hadoop.crypto.key.kms.server.TestKMS$3.call(TestKMS.java:613)
> 2016-10-23 22:05:34 at
> org.apache.hadoop.crypto.key.kms.server.TestKMS$3.call(TestKMS.java:471)
> 2016-10-23 22:05:34 at
> org.apache.hadoop.crypto.key.kms.server.TestKMS.runServer(TestKMS.java:139)
> 2016-10-23 22:05:34 at
> org.apache.hadoop.crypto.key.kms.server.TestKMS.runServer(TestKMS.java:121)
> 2016-10-23 22:05:34 at
> org.apache.hadoop.crypto.key.kms.server.TestKMS.testKMSProvider(TestKMS.java:471)
> 2016-10-23 22:05:34
> 2016-10-23 22:05:34
> 2016-10-23 22:05:34 Results :
> 2016-10-23 22:05:34
> 2016-10-23 22:05:34 Tests in error:
> 2016-10-23 22:05:34
> TestKMS.testKMSProvider:471->runServer:121->runServer:139 ? IO HTTP status
> [40...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
