You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2019/09/17 10:35:00 UTC
[jira] [Resolved] (HADOOP-16371) Option to disable GCM for SSL
connections when running on Java 8
[ https://issues.apache.org/jira/browse/HADOOP-16371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved HADOOP-16371.
-------------------------------------
Fix Version/s: 3.3.0
Resolution: Fixed
> Option to disable GCM for SSL connections when running on Java 8
> ----------------------------------------------------------------
>
> Key: HADOOP-16371
> URL: https://issues.apache.org/jira/browse/HADOOP-16371
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Sahil Takiar
> Assignee: Sahil Takiar
> Priority: Major
> Fix For: 3.3.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org