[
https://issues.apache.org/jira/browse/HADOOP-16256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16822207#comment-16822207
]
Steve Loughran commented on HADOOP-16256:
-----------------------------------------
no reason not to add this; submit a patch. Test wise, not sure what to do.
Something to test invalid values are either compensated for or rejected
(negative numbers), and there's a special Configuration method to get a time
which you should use from the start.
submit a github PR referencing this JIRA, and we'll see what the test run says
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
