[
https://issues.apache.org/jira/browse/HADOOP-11183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346067#comment-14346067
]
Steve Loughran commented on HADOOP-11183:
-----------------------------------------
+1
* Tested locally; 6 MB upload actually took "5.504" seconds, which is
surprisingly fast, but I couldn't see any evidence that it hadn't happened, and
as a regular one to 1.7s, it scaled proportionally to the 6x size increase.
* saw an intermittent failure of
{{TestS3AFileSystemContract.testRenameRootDirForbidden()}} which is something
seen before, and unrelated to this patch.
* docs clearer now
* javadoc and javadoc warnings appear unrelated
* core test failure is the intermittent ZK one again.
applying, Thanks!
> Memory-based S3AOutputstream
> ----------------------------
>
> Key: HADOOP-11183
> URL: https://issues.apache.org/jira/browse/HADOOP-11183
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.6.0
> Reporter: Thomas Demoor
> Assignee: Thomas Demoor
> Attachments: HADOOP-11183-004.patch, HADOOP-11183-005.patch,
> HADOOP-11183-006.patch, HADOOP-11183-007.patch, HADOOP-11183-008.patch,
> HADOOP-11183-009.patch, HADOOP-11183-010.patch, HADOOP-11183.001.patch,
> HADOOP-11183.002.patch, HADOOP-11183.003.patch, design-comments.pdf
>
>
> Currently s3a buffers files on disk(s) before uploading. This JIRA
> investigates adding a memory-based upload implementation.
> The motivation is evidently performance: this would be beneficial for users
> with high network bandwidth to S3 (EC2?) or users that run Hadoop directly on
> an S3-compatible object store (FYI: my contributions are made in name of
> Amplidata).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
