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.