[
https://issues.apache.org/jira/browse/HADOOP-18245?focusedWorklogId=772159&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-772159
]
ASF GitHub Bot logged work on HADOOP-18245:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 18/May/22 22:27
Start Date: 18/May/22 22:27
Worklog Time Spent: 10m
Work Description: kerneltime opened a new pull request, #4329:
URL: https://github.com/apache/hadoop/pull/4329
…Exception
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
Based on production workload, we found that it is not enough to map just
SSLHandshakeException to ConnectException in Loadbalancing KMS Client but that
needs to be extended to SSLExceptions and SocketExceptions.
### How was this patch tested?
Updated existing unit tests.
### For code changes:
- [X] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
Issue Time Tracking
-------------------
Worklog Id: (was: 772159)
Remaining Estimate: 0h
Time Spent: 10m
> Extend KMS related exceptions that get mapped to ConnectException
> ------------------------------------------------------------------
>
> Key: HADOOP-18245
> URL: https://issues.apache.org/jira/browse/HADOOP-18245
> Project: Hadoop Common
> Issue Type: Bug
> Components: kms
> Reporter: Ritesh H Shukla
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Based on production workload, we found that it is not enough to map just
> SSLHandshakeException to ConnectException in Loadbalancing KMS Client but
> that needs to be extended to SSLExceptions and SocketExceptions.
> Sample JDK code that can raise these exceptions:
> https://github.com/openjdk/jdk/blob/jdk-18%2B32/src/java.base/share/classes/sun/security/ssl/SSLSocketImpl.java#L1409-L1428
> Sample Exception backtrace:
> 22/04/13 16:25:53 WARN kms.LoadBalancingKMSClientProvider: KMS provider at
> [https://bdgtr041x10h5.nam.nsroot.net:16001/kms/v1/] threw an IOException:
> javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake
> at sun.security.ssl.SSLSocketImpl.handleEOF(SSLSocketImpl.java:1470)
> at sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1298)
> at
> sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1199)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:373)
> at
> sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:587)
> at
> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDe
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
> at
> sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:480)
> at
> sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:469)
> ... 59 more
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
