Description
We have found that when running the S3AFileSystem, it picks GCM as the ssl cipher suite. Unfortunately this is well known to be slow on java 8: https://stackoverflow.com/questions/25992131/slow-aes-gcm-encryption-and-decryption-with-java-8u20.
In practice we have seen that it can take well over 50% of our CPU time in spark workflows. We should add an option to set the list of cipher suites we would like to use.
Attachments
Attachments
Issue Links
- breaks
-
HADOOP-16321 ITestS3ASSL+TestOpenSSLSocketFactory failing with java.lang.UnsatisfiedLinkErrors
- Resolved
- causes
-
HADOOP-16347 MapReduce job tasks fails on S3A ssl3_get_server_certificate:certificate verify
- Resolved
- is related to
-
HADOOP-16346 Stabilize S3A OpenSSL support
- Resolved
-
HADOOP-16405 Upgrade Wildfly Openssl version to 1.0.7.Final
- Resolved
- relates to
-
HADOOP-15669 ABFS: Improve HTTPS Performance
- Resolved
-
HADOOP-16371 Option to disable GCM for SSL connections when running on Java 8
- Resolved
-
IMPALA-8577 Crash during OpenSSLSocket.read
- Resolved
-
HADOOP-15965 Upgrade to ADLS SDK which has major performance improvement for ingress/egress
- Resolved
- links to