[
https://issues.apache.org/jira/browse/HADOOP-11867?focusedWorklogId=707741&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-707741
]
ASF GitHub Bot logged work on HADOOP-11867:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 12/Jan/22 18:01
Start Date: 12/Jan/22 18:01
Worklog Time Spent: 10m
Work Description: steveloughran commented on pull request #3499:
URL: https://github.com/apache/hadoop/pull/3499#issuecomment-1011311271
OK, I've had a look at the recent changes, and had some shared screen
reviews over zoom
here's what I propose
* create a feature branch in the asf repo where we can rebase/reorder
commits
* get what is done in as the base commit
* then we can split work on the final changes up into new PRs, each with
their own JIRA.
where those changes can be
* buffer pooling (API to these calls and better weak reference handling in
the elastic one or nearby)
* s3a split handling
* huge file support (new tests in the s3a huge file suite)
then, once happy we can do a rebase followed by merge commit into
trunk/branch-3.
key point: this patch has been going and is ready to stabilize, which can be
done with incremental changes in a feature branch.
--
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: 707741)
Time Spent: 9h 50m (was: 9h 40m)
> FS API: Add a high-performance vectored Read to FSDataInputStream API
> ---------------------------------------------------------------------
>
> Key: HADOOP-11867
> URL: https://issues.apache.org/jira/browse/HADOOP-11867
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs, fs/azure, fs/s3, hdfs-client
> Affects Versions: 3.0.0
> Reporter: Gopal Vijayaraghavan
> Assignee: Mukund Thakur
> Priority: Major
> Labels: performance, pull-request-available
> Time Spent: 9h 50m
> Remaining Estimate: 0h
>
> The most significant way to read from a filesystem in an efficient way is to
> let the FileSystem implementation handle the seek behaviour underneath the
> API to be the most efficient as possible.
> A better approach to the seek problem is to provide a sequence of read
> locations as part of a single call, while letting the system schedule/plan
> the reads ahead of time.
> This is exceedingly useful for seek-heavy readers on HDFS, since this allows
> for potentially optimizing away the seek-gaps within the FSDataInputStream
> implementation.
> For seek+read systems with even more latency than locally-attached disks,
> something like a {{readFully(long[] offsets, ByteBuffer[] chunks)}} would
> take of the seeks internally while reading chunk.remaining() bytes into each
> chunk (which may be {{slice()}}ed off a bigger buffer).
> The base implementation can stub in this as a sequence of seeks + read() into
> ByteBuffers, without forcing each FS implementation to override this in any
> way.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
