From hdfs-issues-return-210912-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Fri Feb 23 10:02:07 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 EF3DE18067E for ; Fri, 23 Feb 2018 10:02:06 +0100 (CET) Received: (qmail 61294 invoked by uid 500); 23 Feb 2018 09:02:05 -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 61278 invoked by uid 99); 23 Feb 2018 09:02:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Feb 2018 09:02:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 5FFB51A01FD for ; Fri, 23 Feb 2018 09:02:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -102.311 X-Spam-Level: X-Spam-Status: No, score=-102.311 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id xOyaFGA_CMuh for ; Fri, 23 Feb 2018 09:02:04 +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 07E225FC75 for ; Fri, 23 Feb 2018 09:02:04 +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 3BDB8E00D3 for ; Fri, 23 Feb 2018 09:02:03 +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 24F2B21907 for ; Fri, 23 Feb 2018 09:02:01 +0000 (UTC) Date: Fri, 23 Feb 2018 09:02:01 +0000 (UTC) From: "Elek, Marton (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-11686) Ozone: Support CopyContainer MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-11686?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Elek, Marton updated HDFS-11686: -------------------------------- Attachment: HDFS-11686-HDFS-7240.001.patch > Ozone: Support CopyContainer > ---------------------------- > > Key: HDFS-11686 > URL: https://issues.apache.org/jira/browse/HDFS-11686 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ozone > Reporter: Anu Engineer > Assignee: Elek, Marton > Priority: Major > Labels: OzonePostMerge > Attachments: HDFS-11686-HDFS-7240.001.patch, HDFS-11686-HDFS-7240= .wip.patch > > > Once a container is closed we need to copy the container to the correct p= ool or re-encode the container to use erasure coding. The copyContainer all= ows users to get the container as a tarball from the remote machine. > The copyContainer is a basic step to move the raw container data from one= datanode to an other node. It could be used by higher level components suc= h like the scm which ensures that the replication rules are satisfied. > The CopyContainer by default works in pull model: the destination datanod= e could read the raw data from one or more source datanode where the contai= ner exists. > The source provides a binary representation of the container over a commo= n interface which has two method: > # prepare(containerName) > # copyData(String containerName, OutputStream destination) > Prepare phase is called right after the closing event and the implementat= ion could prepare for the copy by=C2=A0precreate a compressed tar file=C2= =A0from the container data. As a first step we can provide a simple impleme= ntation which creates the tar files on demand. > The destination datanode should retry the copy if the container in the so= urce node not yet prepared. > The raw container data is provided over HTTP. The HTTP endpoint should be= separated from the=C2=A0ObjectStore =C2=A0REST API (similar to the=C2=A0di= stinctions between HDFS-7240 and HDFS-13074)=C2=A0 > Long-term the HTTP endpoint should support Http-Range requests: One conta= iner could be copied from multiple source by the destination.=C2=A0 -- 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