[
https://issues.apache.org/jira/browse/HADOOP-19279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884185#comment-17884185
]
ASF GitHub Bot commented on HADOOP-19279:
-----------------------------------------
manika137 commented on PR #7055:
URL: https://github.com/apache/hadoop/pull/7055#issuecomment-2370618888
> Hey @manika137 I don't see any update on the jira. could you please point
out what have you updated thanks
>
> btw I have updated the release notes here
https://issues.apache.org/jira/browse/HADOOP-19120 saying this is just an
addition. default is still old JDK HTTP client.
Hey @mukund-thakur, sorry, I updated the other release note. Thanks for
updating it!
Should I add details for the default change as well here
https://issues.apache.org/jira/browse/HADOOP-19120?
> ABFS: Disabling Apache Http Client as Default Http Client for ABFS Driver
> -------------------------------------------------------------------------
>
> Key: HADOOP-19279
> URL: https://issues.apache.org/jira/browse/HADOOP-19279
> Project: Hadoop Common
> Issue Type: Task
> Components: fs/azure
> Affects Versions: 3.4.0, 3.4.1
> Reporter: Manika Joshi
> Assignee: Manika Joshi
> Priority: Minor
> Labels: pull-request-available
>
> As part of work done under HADOOP-19120 [ABFS]: ApacheHttpClient adaptation
> as network library - ASF JIRA
> Apache Http Client was introduced as an alternative Network Library that can
> be used with ABFS Driver. Earlier JDK Http Client was the only supported
> network library.
> Apache Http Client was found to be more helpful in terms of controls and
> knobs it provides to better manage the Network aspects of driver. Hence it
> was made the default Network Client to be used with ABFS Driver.
> Recently while running scale workloads, we observed a regression where some
> unexpected wait time was observed while establishing connections. A possible
> fix has been identified and we are working on getting it fixed.
> One scenario identified during internal tests revealed that, with the current
> Apache client implementation, a connection cannot become stale. As a result,
> it is safe to remove the check for stale connections when closing them. This
> change will optimize the connection handling process by eliminating
> unnecessary delays and reducing the risk of potential failures caused by
> redundant checks.
> There was also a possible NPE scenario which was identified on the new
> network client code recently.
> Until we are done with the code fixes and have revalidated the whole Apache
> client flow, we would like to make JDK Client as default client again. The
> new support for Apache Http Client will still be there, but it will be
> disabled behind a config.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
