From hdfs-issues-return-218951-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Mon Apr 30 14:35:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 75F48180647 for ; Mon, 30 Apr 2018 14:35:04 +0200 (CEST) Received: (qmail 95666 invoked by uid 500); 30 Apr 2018 12:35:03 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 95646 invoked by uid 99); 30 Apr 2018 12:35:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Apr 2018 12:35:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 71791CC06F for ; Mon, 30 Apr 2018 12:35:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id mKyaRm6o0Hnm for ; Mon, 30 Apr 2018 12:35:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 851CE5F1BE for ; Mon, 30 Apr 2018 12:35:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id DE50AE129D for ; Mon, 30 Apr 2018 12:35:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 48CE221299 for ; Mon, 30 Apr 2018 12:35:00 +0000 (UTC) Date: Mon, 30 Apr 2018 12:35:00 +0000 (UTC) From: "Ewan Higgs (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-13186) [PROVIDED Phase 2] Multipart Multinode uploader API + Implementations 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/HDFS-13186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458530#comment-16458530 ] Ewan Higgs commented on HDFS-13186: ----------------------------------- 004 - MPU learns abort. - FS MPU::complete forces ordering of parts. - further tests to assert the aforementioned features. > [PROVIDED Phase 2] Multipart Multinode uploader API + Implementations > --------------------------------------------------------------------- > > Key: HDFS-13186 > URL: https://issues.apache.org/jira/browse/HDFS-13186 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Ewan Higgs > Assignee: Ewan Higgs > Priority: Major > Attachments: HDFS-13186.001.patch, HDFS-13186.002.patch, HDFS-13186.003.patch, HDFS-13186.004.patch > > > To write files in parallel to an external storage system as in HDFS-12090, there are two approaches: > # Naive approach: use a single datanode per file that copies blocks locally as it streams data to the external service. This requires a copy for each block inside the HDFS system and then a copy for the block to be sent to the external system. > # Better approach: Single point (e.g. Namenode or SPS style external client) and Datanodes coordinate in a multipart - multinode upload. > This system needs to work with multiple back ends and needs to coordinate across the network. So we propose an API that resembles the following: > {code:java} > public UploadHandle multipartInit(Path filePath) throws IOException; > public PartHandle multipartPutPart(InputStream inputStream, > int partNumber, UploadHandle uploadId) throws IOException; > public void multipartComplete(Path filePath, > List> handles, > UploadHandle multipartUploadId) throws IOException;{code} > Here, UploadHandle and PartHandle are opaque handlers in the vein of PathHandle so they can be serialized and deserialized in hadoop-hdfs project without knowledge of how to deserialize e.g. S3A's version of a UpoadHandle and PartHandle. > In an object store such as S3A, the implementation is straight forward. In the case of writing multipart/multinode to HDFS, we can write each block as a file part. The complete call will perform a concat on the blocks. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org