[
https://issues.apache.org/jira/browse/HADOOP-17853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405167#comment-17405167
]
Steve Loughran commented on HADOOP-17853:
-----------------------------------------
This could be really interesting, especially for those operations which are
very high latency now.
I actually believe some of the ABFS latencies are actually due to java.net code
not using connection pools, so every HEAD request forcing a full TLS
negotiation. There are still plenty of opportunities to speed that up.
I think what I've been looking for here is
* something which can be understood/maintained by people outside the developer
team
* docs & tests
* IOStatistics collection
* meaningful errors when you try and turn it on outside of Azure
* the existing REST API not being treated as "legacy". it's the one I'll be
testing from my laptop and the one which will be used everywhere outside of
Azure.
> ABFS: Enable optional store connectivity over azure specific protocol for
> data egress
> -------------------------------------------------------------------------------------
>
> Key: HADOOP-17853
> URL: https://issues.apache.org/jira/browse/HADOOP-17853
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.4.0
> Reporter: Sneha Vijayarajan
> Assignee: Sneha Vijayarajan
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This Jira is to provide an option to enable store access on read path over an
> Azure specific protocol. This will only work on Azure VMs and hence will be
> disabled by default.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
