[
https://issues.apache.org/jira/browse/HADOOP-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-13560:
------------------------------------
Attachment: HADOOP-13560-branch-2-002.patch
HADOOP-13560 patch 002
block streaming is in, testing at moderate scale <100 MB.
you can choose for buffer-by-ram (current fast uploader) or buffer by HDD; in a
test using SSD & remote S3, I got ~1.38MB/s bandwidth, got something similar
1.44 on RAM. But: we shouldn't run out off heap on the HDD option. RAM
buffering uses existing ByteArrays, to ease source code migration off
FastUpload (which is still there, for now).
* Next: the multi GB tests
* I do plan to add pooled ByteBuffers
* Add metrics of total and ongoing upload, including tracking what quantity of
the outstanding block data has actually been uploaded.
> S3A to support huge file writes and operations -with tests
> ----------------------------------------------------------
>
> Key: HADOOP-13560
> URL: https://issues.apache.org/jira/browse/HADOOP-13560
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.9.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Attachments: HADOOP-13560-branch-2-001.patch,
> HADOOP-13560-branch-2-002.patch
>
>
> An AWS SDK [issue|https://github.com/aws/aws-sdk-java/issues/367] highlights
> that metadata isn't copied on large copies.
> 1. Add a test to do that large copy/rname and verify that the copy really
> works
> 2. Verify that metadata makes it over.
> Verifying large file rename is important on its own, as it is needed for very
> large commit operations for committers using rename
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
