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 42C9717385 for ; Fri, 24 Apr 2015 16:29:42 +0000 (UTC) Received: (qmail 87339 invoked by uid 500); 24 Apr 2015 16:29:39 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 87286 invoked by uid 500); 24 Apr 2015 16:29: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 87080 invoked by uid 99); 24 Apr 2015 16:29:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Apr 2015 16:29:38 +0000 Date: Fri, 24 Apr 2015 16:29:38 +0000 (UTC) From: "Arpit Agarwal (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-8244) HDFS Custom Storage Tier Policies 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-8244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDFS-8244: -------------------------------- Description: Feature request to be able to define custom HDFS storage policies. For example, being able to define DISK:2, Archive:n - 2. Motivation for this is when integrating the archive tier on another cheaper storage system such as Hedvig which we are not in control of and want to hedge our bets in case something goes wrong with that archive storage system (it's new and unproven) we don't want just one copy of the data left on our cluster in case we lose a node. was: Feature request to be able to define custom HDFS storage policies. For example, being able to define DISK:2, Archive:n - 2. Motivation for this is when integrating the archive tier on another cheaper storage system such as Hedvig which we are not in control of and want to hedge our bets in case something goes wrong with that archive storage system (it's new and unproven) we don't want just one copy of the data left on our cluster in case we lose a node. Hari Sekhon http://www.linkedin.com/in/harisekhon > HDFS Custom Storage Tier Policies > --------------------------------- > > Key: HDFS-8244 > URL: https://issues.apache.org/jira/browse/HDFS-8244 > Project: Hadoop HDFS > Issue Type: New Feature > Components: balancer & mover, datanode, HDFS, hdfs-client, namenode > Affects Versions: 2.6.0 > Environment: HDP 2.2 > Reporter: Hari Sekhon > Priority: Minor > > Feature request to be able to define custom HDFS storage policies. > For example, being able to define DISK:2, Archive:n - 2. > Motivation for this is when integrating the archive tier on another cheaper storage system such as Hedvig which we are not in control of and want to hedge our bets in case something goes wrong with that archive storage system (it's new and unproven) we don't want just one copy of the data left on our cluster in case we lose a node. -- This message was sent by Atlassian JIRA (v6.3.4#6332)