hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HADOOP-13047) S3a Forward seek in stream length to be configurable
Date Thu, 12 May 2016 18:26:12 GMT

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

Steve Loughran resolved HADOOP-13047.
    Resolution: Duplicate

> 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
> 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

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

View raw message