Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-18245

Extend KMS related exceptions that get mapped to ConnectException

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 3.4.0
    • 3.4.0
    • kms
    • Reviewed

    Description

      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

      Attachments

        Issue Links

          Activity

            People

              ritesh Ritesh Shukla
              ritesh Ritesh Shukla
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 40m
                  40m