You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/05/06 16:29:13 UTC

[jira] [Assigned] (HADOOP-13047) S3a Forward seek in stream length to be configurable

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

Steve Loughran reassigned HADOOP-13047:
---------------------------------------

    Assignee: Steve Loughran

> S3a Forward seek in stream length to be configurable
> ----------------------------------------------------
>
>                 Key: HADOOP-13047
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13047
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 2.8.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: HADOOP-13047.WIP.2.patch, HADOOP-13047.WIP.patch
>
>
> Even with lazy seek, tests can show that sometimes a short-distance forward seek is triggering a close + reopen, because the threshold for the seek is simply available bytes in the inner stream.
> A configurable threshold would allow data to be read and discarded before that seek. This should be beneficial over long-haul networks as the time to set up the TCP channel is high, and TCP-slow-start means that the ramp up of bandwidth is slow. In such deployments, it will better to read forward than re-open, though the exact "best" number will vary with client and endpoint.



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

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