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

Posted to common-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/04/21 21:10:25 UTC

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

Steve Loughran created HADOOP-13047:
---------------------------------------

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


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)