[HADOOP-16346] Stabilize S3A OpenSSL support

• Type: Sub-task
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 3.3.0
• Fix Version/s: 3.3.0
• Component/s: fs/s3
• Assignee: Sahil Takiar
• Reporter: Steve Loughran
• Created: 04/Jun/19 10:22
• Updated: 16/Nov/20 20:12
• Resolved: 21/Jan/20 16:54

Description

HADOOP-16050 switched S3A to trying to use OpenSSL. We need to make sure this is stable, that people know it exists and aren't left wondering why things which did work have now stopped. Which, given I know who will end up with those support calls, is not something I want.

• Set the default back to the original JDK version.
• Document how to change this so you don't need to use an IDE to work out what other values are allowed
• core-default.xml to include the default value and the text listing the other options.

+ anything else

Issue Links

• causes: HADOOP-16855 ABFS: hadoop-dist fails to add wildfly in class path for hadoop-azure
• depends upon: HADOOP-16347 MapReduce job tasks fails on S3A ssl3_get_server_certificate:certificate verify
• is related to: HADOOP-16405 Upgrade Wildfly Openssl version to 1.0.7.Final
• is related to: HADOOP-16835 catch and downgrade all exceptions trying to load openssl native libs through wildfly
• relates to: HADOOP-16050 S3A SSL connections should use OpenSSL
• relates to: HADOOP-16371 Option to disable GCM for SSL connections when running on Java 8
• relates to: HADOOP-16986 s3a to not need wildfly on the classpath
• relates to: HADOOP-16321 ITestS3ASSL+TestOpenSSLSocketFactory failing with java.lang.UnsatisfiedLinkErrors
• relates to: IMPALA-8577 Crash during OpenSSLSocket.read
• links to: GitHub Pull Request #1764