Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ED01217D29 for ; Thu, 12 Feb 2015 16:08:13 +0000 (UTC) Received: (qmail 9823 invoked by uid 500); 12 Feb 2015 16:08:13 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 9771 invoked by uid 500); 12 Feb 2015 16:08:13 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 9759 invoked by uid 99); 12 Feb 2015 16:08:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Feb 2015 16:08:13 +0000 Date: Thu, 12 Feb 2015 16:08:13 +0000 (UTC) From: "Thomas Demoor (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HADOOP-11183) Memory-based S3AOutputstream MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-11183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Demoor updated HADOOP-11183: ----------------------------------- Attachment: (was: info-S3AFastOutputStream-sync.md) > 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.001.patch, HADOOP-11183.002.patch, HADOOP-11183.003.patch > > > 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)