Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
2.8.0
-
None
-
None
Description
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.
Attachments
Attachments
Issue Links
- Is contained by
-
HADOOP-13028 add low level counter metrics for S3A; use in read performance tests
- Resolved