[
https://issues.apache.org/jira/browse/HADOOP-16256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18047160#comment-18047160
]
ASF GitHub Bot commented on HADOOP-16256:
-----------------------------------------
github-actions[bot] commented on PR #774:
URL: https://github.com/apache/hadoop/pull/774#issuecomment-3684629209
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> HTTPFileSystem disallows users from configuring the connectionTimeout and
> readTimeout of HttpClient.
> ----------------------------------------------------------------------------------------------------
>
> Key: HADOOP-16256
> URL: https://issues.apache.org/jira/browse/HADOOP-16256
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Shanthoosh Venkataraman
> Priority: Major
>
> HADOOP-14383 added a Hadoop filesystem API implementation to localize
> resources from HTTP server for container localization.
> Currently HttpFileSystem uses the default HttpClient connectionTimeout and
> readTimeout, which is infinity in most JVM.
> When the HTTP server is slow, this prolongs the execution time of the
> container localization phase and in some cases we've observed that it runs
> for hours.
> It would be better to choose reasonable defaults for connectionTimeout and
> readTimeout of HttpClient and allow users to configure them.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
