Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-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 4F34318CBC for ; Mon, 27 Apr 2015 07:53:39 +0000 (UTC) Received: (qmail 60343 invoked by uid 500); 27 Apr 2015 07:53:39 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 60275 invoked by uid 500); 27 Apr 2015 07:53:39 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 60263 invoked by uid 99); 27 Apr 2015 07:53:39 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Apr 2015 07:53:39 +0000 Date: Mon, 27 Apr 2015 07:53:39 +0000 (UTC) From: "Li Bo (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-8015) Erasure Coding: local and remote block writer for coding work in DataNode 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-8015?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14513= 671#comment-14513671 ]=20 Li Bo commented on HDFS-8015: ----------------------------- hi, Yi I think there=E2=80=99re several ways to handle writing a decoded block to = remote or local. My idea is that first get a domain socket which is bound a= nd listened by {{DataNode#localDataXCeriverServer}}, then write data via th= e output stream of this socket. The advantage is that we don=E2=80=99t need= to handle the details of block writing. The next step is to extend {{Block= Receiver}}. Currently it writes to local disk and may also write to remote.= We can add a switcher to control its writing directions, i.e, only local,= only remote, remote + local. We can discuss this issue after your first pa= tch is ready.=20 > Erasure Coding: local and remote block writer for coding work in DataNode > ------------------------------------------------------------------------- > > Key: HDFS-8015 > URL: https://issues.apache.org/jira/browse/HDFS-8015 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Kai Zheng > Assignee: Li Bo > Attachments: HDFS-8015-000.patch > > > As a task of HDFS-7344 ECWorker, in either stripping or non-stripping era= sure coding, to perform encoding or decoding, we need to be able to write d= ata blocks locally or remotely. This is to come up block writer facility in= DataNode side. Better to think about the similar work done in client side,= so in future it's possible to unify the both. -- This message was sent by Atlassian JIRA (v6.3.4#6332)