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 "Steven Rand (Jira)" <ji...@apache.org> on 2019/09/13 00:58:00 UTC

[jira] [Created] (HADOOP-16569) improve TLS performance for NativeAzureFileSystem

Steven Rand created HADOOP-16569:
------------------------------------

             Summary: improve TLS performance for NativeAzureFileSystem
                 Key: HADOOP-16569
                 URL: https://issues.apache.org/jira/browse/HADOOP-16569
             Project: Hadoop Common
          Issue Type: Improvement
            Reporter: Steven Rand


Several tickets have already discussed the performance issues of GCM ciphers on jdk8 in relation to cloud connectors:

* HADOOP-16050, HADOOP-16371 (s3a)
* HADOOP-15669 (abfs)
* HADOOP-15965 (adls)

However, we haven't gotten around to fixing this for Azure Blob Store yet (the wasbs scheme).

It would be helpful to reuse the {{SSLSocketFactoryEx}} class that was added in HADOOP-15669. The {{getInstrumentedContext}} method in {{AzureNativeFileSystemStore}} can already mutate the connection to the blob store and inject that socket factory, so it's not a hard change to make.

This isn't necessarily blocked on HADOOP-16371, but it would  be helpful if we merged that PR first, since it moves the custom {{SSLSocketFactory}} that uses wildfly-openssl out of the code that's specific to ABFS and into a place where the Azure Blob Store code can access it.

Tagging [~stakiar] since you've been working on this for the other cloud connectors



--
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