[
https://issues.apache.org/jira/browse/HDFS-5219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770162#comment-13770162
]
Jing Zhao commented on HDFS-5219:
---------------------------------
HDFS-5123/HDFS-5221 are addressing the same issue for hftp, and they may use a
similar retry mechanism. Since these retry operations are all over http, will
it make sense to let them share the same retry configuration properties? In
that case, we can rename the new configuration from *_WEBHDFS_* to something
like *_HTTP_*?
> Add configuration keys for WebHDFS
> ----------------------------------
>
> Key: HDFS-5219
> URL: https://issues.apache.org/jira/browse/HDFS-5219
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
> Reporter: Haohui Mai
> Assignee: Haohui Mai
> Attachments: HDFS-5219.000.patch, HDFS-5219.001.patch
>
>
> Currently the WebHDFS client reuses the configuration of DFSClient to
> construct its RetryPolicy. This is problematic because:
> 1. It makes the WebHDFS client depends on the DFSClient.
> 2. The default values of the RetryPolicy of DFSClient might be ill fit for
> the WebHDFS client, which transfers all data using HTTP.
> This JIRA proposes to introduce new configuration keys for WebHDFS to resolve
> this problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
