Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id AEDC4200C2F for ; Mon, 6 Mar 2017 20:48:40 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id AD206160B81; Mon, 6 Mar 2017 19:48:40 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 012CF160B76 for ; Mon, 6 Mar 2017 20:48:39 +0100 (CET) Received: (qmail 40870 invoked by uid 500); 6 Mar 2017 19:48:39 -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 40859 invoked by uid 99); 6 Mar 2017 19:48:39 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Mar 2017 19:48:39 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 97B9D185CAB for ; Mon, 6 Mar 2017 19:48:38 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -2.347 X-Spam-Level: X-Spam-Status: No, score=-2.347 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-2.999, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id pA3NPJVHR89l for ; Mon, 6 Mar 2017 19:48:37 +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 319E05FC75 for ; Mon, 6 Mar 2017 19:48:37 +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 23CB4E2AC6 for ; Mon, 6 Mar 2017 19:48:35 +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 1F664241CC for ; Mon, 6 Mar 2017 19:48:34 +0000 (UTC) Date: Mon, 6 Mar 2017 19:48:34 +0000 (UTC) From: "Andrew Wang (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-11503) Integrate Chocolate Cloud RS coder implementation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 06 Mar 2017 19:48:40 -0000 [ https://issues.apache.org/jira/browse/HDFS-11503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897919#comment-15897919 ] Andrew Wang commented on HDFS-11503: ------------------------------------ From [~sw0rdf1sh]: {quote} Our understanding is that this is the intended way of shipping new native EC plugins. Some glue code is always necessary in the framework (like with Liberasurecode). Isn't this the case? {quote} Yes, for sure. Glue code is definitely fine. My concern though is that if CC's RS implementation isn't bit-identical to ISA-L and the Java coder, then users won't be able to transparently swap out the coder implementations. In this case, we'll need to add additional guardrails in the form of new "erasure coding policies" which encapsulate the coder and its parameters (e.g. CC-RS 6+3 with a 64KB cell size). We only have 5 supported policies right now, so adding CC-RS would greatly increase this configuration space. > Integrate Chocolate Cloud RS coder implementation > ------------------------------------------------- > > Key: HDFS-11503 > URL: https://issues.apache.org/jira/browse/HDFS-11503 > Project: Hadoop HDFS > Issue Type: New Feature > Components: erasure-coding > Affects Versions: 3.0.0-alpha2 > Reporter: Andrew Wang > Assignee: Marcell Feher > > Quote from Marcell on HDFS-7285: > First of all let me introduce ourselves: we are Chocolate Cloud from Denmark, we use erasure coding to improve storage solutions. We already have Reed-Solomon and Random Linear Network Coding backends for Liberasurecode, and now we are at the final stage of developing our RS plugin to HDFS-EC. The performance of our plugin is similar to ISA-L's, in some configurations we are better, in others we are worse (our initial speed comparison charts can be found here: https://www.chocolate-cloud.cc/Plugins/HDFS-EC/hdfs.html). > We would like our plugin to become officially supported in Hadoop 3.0. We can already provide a preliminary version of our (native) library and a patch with the necessary glue code for the next alpha release. > I'd like to know your thoughts about whether it's possible and how it could be achieved. > P.S: I'm happy to share more details if there's interest -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org