[HADOOP-16371] Option to disable GCM for SSL connections when running on Java 8

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.3.0
• Component/s: fs/s3
• Assignee: Sahil Takiar
• Reporter: Sahil Takiar
• Created: 13/Jun/19 19:37
• Updated: 02/Nov/20 13:25
• Resolved: 17/Sep/19 10:34

Description

This was the original objective of HADOOP-16050. HADOOP-16050 was changed to mimic HADOOP-15669 and added (or attempted to add) support for Wildfly-OpenSSL in S3A.

Due to the number of issues have seen with S3A + WildFly OpenSSL (see HADOOP-16346), HADOOP-16050 was reverted.

As shown in the description of HADOOP-16050, and the analysis done in HADOOP-15669, GCM has major performance issues when running on Java 8. Removing it from the list of available ciphers can drastically improve performance, perhaps not as much as using OpenSSL, but still a considerable amount.

Issue Links

• breaks: HADOOP-17337 S3A NetworkBinding has a runtime class dependency on a third-party shaded class
• breaks: HADOOP-16773 Fix duplicate assertj-core dependency in hadoop-common module.
• is related to: HADOOP-16346 Stabilize S3A OpenSSL support
• is related to: HADOOP-15669 ABFS: Improve HTTPS Performance
• is related to: HADOOP-16050 S3A SSL connections should use OpenSSL
• links to: GitHub Pull Request #970