[
https://issues.apache.org/jira/browse/HDFS-6214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966656#comment-13966656
]
Kihwal Lee commented on HDFS-6214:
----------------------------------
Related discussion at
http://stackoverflow.com/questions/9031311/slow-transfers-in-jetty-with-chunked-transfer-encoding-at-certain-buffer-size
So, if "io.file.buffer.size" is small enough, like 4K (the default), it may be
overall slower, but there will be no difference for files > 2GB. Do you know
what the response buffer size is for this type of webhdfs responses from
datanodes?
> Webhdfs has poor throughput for files >2GB
> ------------------------------------------
>
> Key: HDFS-6214
> URL: https://issues.apache.org/jira/browse/HDFS-6214
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Attachments: HDFS-6214.patch
>
>
> For the DN's open call, jetty returns a Content-Length header for files <2GB,
> and uses chunking for files >2GB. A "bug" in jetty's buffer handling results
> in a ~8X reduction in throughput.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
