[
https://issues.apache.org/jira/browse/HDFS-4594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746096#comment-13746096
]
Hudson commented on HDFS-4594:
------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk #1525 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1525/])
HDFS-4594. WebHDFS open sets Content-Length header to what is specified by
length parameter rather than how much data is actually returned. Contributed by
Chris Nauroth. (cnauroth:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1515989)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/web/resources/DatanodeWebHdfsMethods.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/web/TestWebHdfsFileSystemContract.java
> WebHDFS open sets Content-Length header to what is specified by length
> parameter rather than how much data is actually returned.
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-4594
> URL: https://issues.apache.org/jira/browse/HDFS-4594
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
> Affects Versions: 2.0.3-alpha
> Reporter: Arpit Gupta
> Assignee: Chris Nauroth
> Priority: Minor
> Fix For: 3.0.0, 2.1.1-beta
>
> Attachments: HDFS-4594.1.patch
>
>
> This was noticed on 2.0.3 alpha
> Lets say we have a file of length x
> We make an webhdfs open call specifying length=x+1
> The response of the call redirected to the datanode sets the content length
> header to value x+1 rather than x.
> Now this causes an error when the client tries to read the data.
> For the test i was using HttpResponse.getEntity().getContent()
> This failed with message "Premature end of Content-Length delimited message
> body (expected: 71898; received: 71897"
> This was not seen in hadoop 1 as we did not set the content length header.
--
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