[
https://issues.apache.org/jira/browse/HADOOP-16569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929292#comment-16929292
]
Sahil Takiar commented on HADOOP-16569:
---------------------------------------
Hey [~Steven Rand], thanks for tagging me. Yeah, HADOOP-16371 would help here.
I recently updated the PR for HADOOP-16371 -
https://github.com/apache/hadoop/pull/970 and am working on running some
additional testing, but review comments are welcome.
> 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
> Priority: Major
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
