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 10969200C09 for ; Wed, 11 Jan 2017 02:47:00 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 0F370160B4B; Wed, 11 Jan 2017 01:47:00 +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 58A5F160B3D for ; Wed, 11 Jan 2017 02:46:59 +0100 (CET) Received: (qmail 66569 invoked by uid 500); 11 Jan 2017 01:46:58 -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 66550 invoked by uid 99); 11 Jan 2017 01:46:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jan 2017 01:46:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 625482C03DE for ; Wed, 11 Jan 2017 01:46:58 +0000 (UTC) Date: Wed, 11 Jan 2017 01:46:58 +0000 (UTC) From: "Andrew Wang (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-8095) Allow to configure the system default EC schema MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 11 Jan 2017 01:47:00 -0000 [ https://issues.apache.org/jira/browse/HDFS-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816802#comment-15816802 ] Andrew Wang commented on HDFS-8095: ----------------------------------- Got it, thanks for the context Kai. When you say data corruption, do you mean data loss if the cluster has insufficient # datanodes or racks? Overall I like the idea of making this act like the blocksize and replication factor. These are specified by the client and have default values in client configuration, but the NN enforces limits on the values to make sure they're reasonable. Seems related to HDFS-7859. Admins would add all the allowable EC policies, and users would can choose among them. NN would throw an error if an unknown policy is requested. > Allow to configure the system default EC schema > ----------------------------------------------- > > Key: HDFS-8095 > URL: https://issues.apache.org/jira/browse/HDFS-8095 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Kai Zheng > Assignee: Kai Zheng > Labels: hdfs-ec-3.0-nice-to-have > > As suggested by [~umamaheswararao] and [~vinayrpet] in HDFS-8074, we may desire allowing to configure the system default EC schema, so in any deployment a cluster admin may be able to define their own system default one. In the discussion, we have two approaches to configure the system default schema: 1) predefine it in the {{ecschema-def.xml}} file, making sure it's not changed; 2) configure the key parameter values as properties in {{core-site.xml}}. Open this for future consideration in case it's forgotten. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org