Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Fri, 27 Mar 2015 10:58:54 +0000 (UTC)
From: "Thomas Demoor (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12785774.1427343416000.48739.1427453934056@Atlassian.JIRA>
In-Reply-To: <JIRA.12785774.1427343416000@Atlassian.JIRA>
References: <JIRA.12785774.1427343416000@Atlassian.JIRA>
 <JIRA.12785774.1427343416069@arcas>
Subject: [jira] [Commented] (HADOOP-11753)
 TestS3AContractOpen#testOpenReadZeroByteFile fails due to negative range
 header
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Thomas Demoor commented on HADOOP-11753:
----------------------------------------

Probably against Cloudian backend.

Please see the HTTP [spec| https://tools.ietf.org/html/rfc7233#section-2.1]
{quote} An origin server MUST ignore a Range header field that contains a range unit it does not understand. {quote}

If you still use the [old spec | https://tools.ietf.org/html/rfc2616#section-14.35.1]
{quote}The recipient of a byte-range-set that includes one or more syntactically invalid byte-range-spec values MUST ignore the header field that includes that byte-range-set.{quote}

Investigated vs AWS: correct implementation, the request is served as if it would be a non-ranged GET. (f.i.: (0,-1) on a 0-byte object returns 0 bytes,  (0,-1000) on a 4 byte object returns 4 bytes, ...).


> TestS3AContractOpen#testOpenReadZeroByteFile fails due to negative range header
> -------------------------------------------------------------------------------
>
>                 Key: HADOOP-11753
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11753
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 3.0.0, 2.7.0
>            Reporter: Takenori Sato
>            Assignee: Takenori Sato
>         Attachments: HADOOP-11753-branch-2.7.001.patch
>
>
> _TestS3AContractOpen#testOpenReadZeroByteFile_ fails as follows.
> {code}
> testOpenReadZeroByteFile(org.apache.hadoop.fs.contract.s3a.TestS3AContractOpen)  Time elapsed: 3.312 sec  <<< ERROR!
> com.amazonaws.services.s3.model.AmazonS3Exception: Status Code: 416, AWS Service: Amazon S3, AWS Request ID: A58A95E0D36811E4, AWS Error Code: InvalidRange, AWS Error Message: The requested range cannot be satisfied.
> 	at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:798)
> 	at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:421)
> 	at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:232)
> 	at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3528)
> 	at com.amazonaws.services.s3.AmazonS3Client.getObject(AmazonS3Client.java:1111)
> 	at org.apache.hadoop.fs.s3a.S3AInputStream.reopen(S3AInputStream.java:91)
> 	at org.apache.hadoop.fs.s3a.S3AInputStream.openIfNeeded(S3AInputStream.java:62)
> 	at org.apache.hadoop.fs.s3a.S3AInputStream.read(S3AInputStream.java:127)
> 	at java.io.FilterInputStream.read(FilterInputStream.java:83)
> 	at org.apache.hadoop.fs.contract.AbstractContractOpenTest.testOpenReadZeroByteFile(AbstractContractOpenTest.java:66)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> 	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> 	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> 	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> 	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> 	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> 	at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
> {code}
> This is because the header is wrong when calling _S3AInputStream#read_ after _S3AInputStream#open_.
> {code}
> Range: bytes=0--1
> * from 0 to -1
> {code}
> Tested on the latest branch-2.7.
> {quote}
> $ git log
> commit d286673c602524af08935ea132c8afd181b6e2e4
> Author: Jitendra Pandey <Jitendra@Jitendra-Pandeys-MacBook-Pro-4.local>
> Date:   Tue Mar 24 16:17:06 2015 -0700
> {quote}


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