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 E5ADA1784E for ; Thu, 30 Apr 2015 14:44:07 +0000 (UTC) Received: (qmail 48968 invoked by uid 500); 30 Apr 2015 14:44:07 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 48907 invoked by uid 500); 30 Apr 2015 14:44:07 -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 48892 invoked by uid 99); 30 Apr 2015 14:44:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Apr 2015 14:44:07 +0000 Date: Thu, 30 Apr 2015 14:44:07 +0000 (UTC) From: "Uma Maheswara Rao G (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-8137) Sends the EC schema to DataNode as well in EC encoding/recovering command 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-8137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521585#comment-14521585 ] Uma Maheswara Rao G commented on HDFS-8137: ------------------------------------------- Thanks a lot for the review Kai. Good catch. You are right, we are storing in xattrs along with zone. {quote} ECSchemaManager might not be supposed to get a schema associated with a zone, dir/file, but ErasureCodingZoneManager may do. {quote} By mistake I said as ECSchemaManager. Your are right, I should have said as ErasureCodingZoneManager as it has that related code what I was talking. Also I added the getECSchema API in namesystem itself as we have already added some ECSchema related API in FSNameSystem. For reusing the codes from ECZoneManager codes, keeping this new API in namesystem would give us the flexibility, but we can not get the same flexibility from BlockCollection as we can not access FSDirectory details there. Please check if the latest patch make sense for you? > Sends the EC schema to DataNode as well in EC encoding/recovering command > ------------------------------------------------------------------------- > > Key: HDFS-8137 > URL: https://issues.apache.org/jira/browse/HDFS-8137 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Kai Zheng > Assignee: Uma Maheswara Rao G > Attachments: HDFS-8137-0.patch, HDFS-8137-1.patch > > > Discussed with [~umamaheswararao] and [~vinayrpet], we should also send the EC schema to DataNode as well contained in the EC encoding/recovering command. The target DataNode will use it to guide the executing of the task. > Another way would be, DataNode would just request schema actively thru a separate RPC call, and as an optimization consideration, DataNode may cache schemas to avoid repeatedly asking for the same schema twice. -- This message was sent by Atlassian JIRA (v6.3.4#6332)