Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 9 Aug 2017 09:33:00 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.13083117.1498651498000.126417.1502271180478@Atlassian.JIRA>
In-Reply-To: <JIRA.13083117.1498651498000@Atlassian.JIRA>
References: <JIRA.13083117.1498651498000@Atlassian.JIRA> <JIRA.13083117.1498651498220@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HADOOP-14606) S3AInputStream: Handle http stream
 skip(n) skipping < n bytes in a forward seek
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 09 Aug 2017 09:33:05 -0000


     [ https://issues.apache.org/jira/browse/HADOOP-14606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran updated HADOOP-14606:
------------------------------------
    Description: 
There's some hints in the InputStream docs that {{skip(n)}} may skip <n bytes. Codepaths only seem to do this if read() returns -1, meaning end of stream is reached.

If that happens when doing a forward seek via skip, then we have got our numbers wrong and are in trouble. Look for a negative response, log @ ERROR and revert to a close/reopen seek to an absolute position.

*I have no evidence of this acutally occurring*

  was:
There's some hints in the InputStream docs that {{skip(n)}} may skip <n bytes. Codepaths only seem to do this if read() returns -1, meaning end of stream is reached. Wh

If that happens when doing a forward seek via skip, then we have got our numbers wrong and are in trouble. Look for a negative response, log @ ERROR and revert to a close/reopen seek to an absolute position.

*I have no evidence of this acutally occurring*


> S3AInputStream: Handle http stream skip(n) skipping < n bytes in a forward seek
> -------------------------------------------------------------------------------
>
>                 Key: HADOOP-14606
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14606
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 2.8.1
>            Reporter: Steve Loughran
>
> There's some hints in the InputStream docs that {{skip(n)}} may skip <n bytes. Codepaths only seem to do this if read() returns -1, meaning end of stream is reached.
> If that happens when doing a forward seek via skip, then we have got our numbers wrong and are in trouble. Look for a negative response, log @ ERROR and revert to a close/reopen seek to an absolute position.
> *I have no evidence of this acutally occurring*


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org