[
https://issues.apache.org/jira/browse/HADOOP-15245?focusedWorklogId=740899&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-740899
]
ASF GitHub Bot logged work on HADOOP-15245:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 14/Mar/22 14:14
Start Date: 14/Mar/22 14:14
Worklog Time Spent: 10m
Work Description: ahmarsuhail commented on pull request #3927:
URL: https://github.com/apache/hadoop/pull/3927#issuecomment-1066846326
@mukund-thakur @mehakmeet would you be able to take a look at this PR?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 740899)
Time Spent: 2h (was: 1h 50m)
> S3AInputStream.skip() to use lazy seek
> --------------------------------------
>
> Key: HADOOP-15245
> URL: https://issues.apache.org/jira/browse/HADOOP-15245
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.1.0
> Reporter: Steve Loughran
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> the default skip() does a read and discard of all bytes, no matter how far
> ahead the skip is. This is very inefficient if the skip() is being done on
> S3A random IO, though exactly what to do when in sequential mode.
> Proposed:
> * add an optimized version of S3AInputStream.skip() which does a lazy seek,
> which itself will decided when to skip() vs issue a new GET.
> * add some more instrumentation to measure how often this gets used
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
