[jira] [Commented] (HDFS-7163) WebHdfsFileSystem should retry reads according to the configured retry policy.

["Kihwal Lee (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HDFS-7163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081251#comment-15081251 ] 

Kihwal Lee commented on HDFS-7163:
----------------------------------

The build failure is in libwebhdfs native builds.  This is in contrib and only gets built when {{-Drequire.libwebhdfs}} is specified. You might need to install some of the build dependencies such as {{jansson-devel}}  Looks like HDFS-8346.

> WebHdfsFileSystem should retry reads according to the configured retry policy.
> ------------------------------------------------------------------------------
>
>                 Key: HDFS-7163
>                 URL: https://issues.apache.org/jira/browse/HDFS-7163
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: webhdfs
>    Affects Versions: 3.0.0, 2.5.1
>            Reporter: Eric Payne
>            Assignee: Eric Payne
>             Fix For: 3.0.0, 2.7.3
>
>         Attachments: HDFS-7163-branch-2.003.patch, HDFS-7163-branch-2.004.patch, HDFS-7163-branch-2.7.003.patch, HDFS-7163-branch-2.7.004.patch, HDFS-7163-branch-2.7.005.patch, HDFS-7163.001.patch, HDFS-7163.002.patch, HDFS-7163.003.patch, HDFS-7163.004.patch, HDFS-7163.005.patch, WebHDFS Read Retry.pdf
>
>
> In the current implementation of WebHdfsFileSystem, opens are retried according to the configured retry policy, but not reads. Therefore, if a connection goes down while data is being read, the read will fail and the read will have to be retried by the client code.
> Also, after a connection has been established, the next read (or seek/read) will fail and the read will have to be restarted by the client code.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)